5 ms·
It does exactly what the configuration tells it to do. At one point some distributions accidentally configured the sshd or cron unit to do that. People were a
by justinsaccount 5y ago
It does exactly what the configuration tells it to do.
At one point some distributions accidentally configured the sshd or cron unit to do that. People were a bit surprised when restarting sshd or cron killed every single background child process.
See https://www.freedesktop.org/software/systemd/man/systemd.kill.html#KillMode= https://www.freedesktop.org/software/systemd/man/systemd.kil...
Not to mention if k3s is just managing containers running under docker or containerd, those processes are not parentless just because k3s stopped.
- mongol 5y agoMy point is, this feels like an area where there is more work to do. Not surprising, the container landscape is a relatively new and rapidly evolving field that hardly existed when systemd was invented. But the fact that a piece of software supplies a killall.sh script reminds me of the old situation before systemd, when every software provided their own lifecycle scripts.