Timeout for service shutdown in legacy services

Leonid Podolny leonidp.lists at gmail.com
Sun Jun 5 06:52:13 UTC 2011


Hi,
When systemd tries to shutdown a service, after a certain timeout, it
just kills all the processes belonging to this service. There is a
configuration option that allows to change that timeout. However, it
is available only for the new systemd formatI and not for the "legacy"
(i.e. /etc/init.d/*) services.

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.


More information about the users mailing list