Opened 12 years ago
Closed 12 years ago
#3403 closed Enhancement (invalid)
Exit Transmission-daemon nicely.
Reported by: | snake98 | Owned by: | charles |
---|---|---|---|
Priority: | Low | Milestone: | |
Component: | Daemon | Version: | 2.01 |
Severity: | Minor | Keywords: | |
Cc: |
Description
Add an option in Transmission-remote or transmisioncli to shut down the daemon nicely(And save current settings). I currently use kill transmission but sometimes the torrents are not stopped nicely and it has to recheck them. (Which is slow on a router).
If there currently is a way just invalidate the ticket with instructions on how to do it. I was unable to find it in the wiki.
Change History (11)
comment:1 Changed 12 years ago by howl
comment:2 Changed 12 years ago by snake98
As this is running on a headless machine(router) there is no(in my case) /opt/etc/init.d/transmission-daemon
I have to start it manually.
comment:3 Changed 12 years ago by howl
I see, usually routers doesn't have a shutdown sequence, so it's no possible to exit cleanly as you said. Let's see what the devs say, but thinking in this type of devices is an interesting suggestion to provide shutdown from transmission-remote.
comment:4 Changed 12 years ago by Rolcol
Hm... I think killing it closes the daemon cleanly. What signal are you killing it with?
comment:5 follow-up: ↓ 7 Changed 12 years ago by snake98
I just kill + the 4 pids of transmission, should I only use the first one?
comment:6 Changed 12 years ago by charles
- Milestone changed from None Set to 2.10
- Owner set to charles
- Status changed from new to assigned
comment:7 in reply to: ↑ 5 Changed 12 years ago by Longinus00
Replying to snake98:
I just kill + the 4 pids of transmission, should I only use the first one?
What do you mean 'the 4 pids of transmission'.
comment:8 follow-up: ↓ 9 Changed 12 years ago by snake98
I have one transmission running here is my ps command
root@Asus RT-N16:/opt# ps | grep transmission 14436 root 16016 S /opt/bin/transmission-daemon -g /opt/transmission/config 14437 root 16016 S /opt/bin/transmission-daemon -g /opt/transmission/config 14438 root 16016 S /opt/bin/transmission-daemon -g /opt/transmission/config 14440 root 16016 S /opt/bin/transmission-daemon -g /opt/transmission/config 14443 root 16016 D /opt/bin/transmission-daemon -g /opt/transmission/config 14563 root 1528 R grep transmission root@Asus RT-N16:/opt#
comment:9 in reply to: ↑ 8 Changed 12 years ago by Longinus00
Replying to snake98:
I have one transmission running here is my ps command
root@Asus RT-N16:/opt# ps | grep transmission 14436 root 16016 S /opt/bin/transmission-daemon -g /opt/transmission/config 14437 root 16016 S /opt/bin/transmission-daemon -g /opt/transmission/config 14438 root 16016 S /opt/bin/transmission-daemon -g /opt/transmission/config 14440 root 16016 S /opt/bin/transmission-daemon -g /opt/transmission/config 14443 root 16016 D /opt/bin/transmission-daemon -g /opt/transmission/config 14563 root 1528 R grep transmission root@Asus RT-N16:/opt#
You have 5 instances of transmission running.
comment:10 Changed 12 years ago by snake98
It may look that way but I don't 114437 to 14563 are child processes of 14436. I don't know if this matters, but I'm runing on mips processor. for example
root@Asus RT-N16:/opt# ps | grep transmission 14563 root 1528 R grep transmission root@Asus RT-N16:/opt#
nothing is found so I run
root@Asus RT-N16:/opt#/opt/bin/transmission-daemon -g /opt/transmission/config root@Asus RT-N16:/opt# ps | grep transmission 14436 root 16016 S /opt/bin/transmission-daemon -g /opt/transmission/config 14437 root 16016 S /opt/bin/transmission-daemon -g /opt/transmission/config 14438 root 16016 S /opt/bin/transmission-daemon -g /opt/transmission/config 14440 root 16016 S /opt/bin/transmission-daemon -g /opt/transmission/config 14443 root 16016 D /opt/bin/transmission-daemon -g /opt/transmission/config 14563 root 1528 R grep transmission root@Asus RT-N16:/opt#
so you see I only run it once, I think there is a child process for each torrent I have loaded.
comment:11 Changed 12 years ago by charles
- Milestone 2.10 deleted
- Resolution set to invalid
- Status changed from assigned to closed
Actually after re-reading this ticket I agree more with Howl and Rolcol.
There's probably only one actual instance of Transmission running, and ps is getting tripped up by showing you all the different threads.
This could be invalid, the way to cleany stop a system daemon should be provided by the system where the daemon is running.
Ej:
sudo service transmission-daemon stop
/etc/init.d/transmission-daemon stop
...