3 ms·
Yup. And unlike sysvinit Debian systems I run (hundreds under bookworm), systemd init systems (I run thousands) require all sorts of workarounds for this sort
by b112 2y ago
Yup. And unlike sysvinit Debian systems I run (hundreds under bookworm), systemd init systems (I run thousands) require all sorts of workarounds for this sort of behaviour. I get VMs not rebooting due to NFS umount failures, VMs not logging shutdown info because rsyslogd is terminated too early, literally endless issues.
Killing services without a proper TERM and wait prior to -9 is only one of the wonderful shortcomings I find with systemd.
- zokier 2y agoTERM, wait, KILL is exactly what systemd does by default, and it's again configurable (and documented): > If no ExecStop= commands are specified, the service gets the SIGTERM immediately. This default behavior can be changed by the TimeoutStopFailureMode= option. Second, it configures the time to wait for the service itself to stop. If it doesn't terminate in the specified time, it will be forcibly terminated by SIGKILL (see KillMode= in systemd.kill(5)). https://www.freedesktop.org/software/systemd/man/latest/systemd.service.html#TimeoutStopSec= https://www.freedesktop.org/software/systemd/man/latest/syst... https://www.freedesktop.org/software/systemd/man/latest/systemd.kill.html#KillMode= https://www.freedesktop.org/software/systemd/man/latest/syst...