Timeout for service shutdown in legacy services
On Sun, 2011-06-05 at 09:52 +0300, Leonid Podolny wrote:
> The full story goes like this: transmission-daemon has an
> uncharacteristically long shutdown time. Every time the service goes
> down, systemd thinks that it is unresponsive and kills it. It messes
> up the metadata of the seeding (i.e. fully downloaded) torrents and
> when I bring the daemon back up, it thinks that it needs to
> re-download a torrent, even though the actual data is there. I have to
> manually select "Verify the local data" every time I start the daemon
> and it is incredibly annoying.
Maybe you can add the verify step to the transmission-daemon init
script. Or, better, you could create a wrapper script that starts the
daemon and then does the verify.
I know, still shitty.
Also, this sucks because I just started using transmission-daemon
instead of the GTK version in F12, and I've become rather fond of it! I
was planning on setting it up on F15. Fail.
Kanwar Ranbir Sandhu
Linux 22.214.171.124-175.fc12.x86_64 x86_64 GNU/Linux
11:28:39 up 4 days, 4:40, 4 users, load average: 0.10, 0.06, 0.01
users mailing list
To unsubscribe or change subscription options: