diff options
author | Lennart Poettering <lennart@poettering.net> | 2016-07-12 17:18:43 +0200 |
---|---|---|
committer | Lennart Poettering <lennart@poettering.net> | 2016-07-12 17:32:30 +0200 |
commit | d450612953e6881e2dcbbad7e638160b73a83d77 (patch) | |
tree | 6c41913205579f4f5bd517cd7378a19b955c4c6c /sysusers.d | |
parent | 595bfe7df2999cfb99b274ce510695aed4aba6d5 (diff) |
shutdown: use 90s SIGKILL timeout
There's really no reason to use 10s here, let's instead default to 90s like we
do for everything else.
The SIGKILL during the final killing spree is in most regards the fourth level
of a safety net, after all: any normal service should have already been stopped
during the normal service shutdown logic, first via SIGTERM and then SIGKILL,
and then also via SIGTERM during the finall killing spree before we send
SIGKILL. And as a fourth level safety net it should only be required in
exceptional cases, which means it's safe to rais the default timeout, as normal
shutdowns should never be delayed by it.
Note that journald excludes itself from the normal service shutdown, and relies
on the final killing spree to terminate it (this is because it wants to cover
the normal shutdown phase's complete logging). If the system's IO is
excessively slow, then the 10s might not be enough for journald to sync
everything to disk and logs might get lost during shutdown.
Diffstat (limited to 'sysusers.d')
0 files changed, 0 insertions, 0 deletions