On May 21, Marc Lehmann <schm...@schmorp.de> wrote: > The semantic that debian used before and is used by similar programs (such > as sshd) is obviously the right one - killing everything that was ever > started directly or indirectly from inetd is obviously wrong? I am not sure: if I stop inetd then I want to stop all running daemons, not just prevent new connections.
> > Can you better describe your setup? Which kind of shells were you > > spawning from inetd? > Anything gets killed, not just shells - I can start a screen session with > e.g. "nohup gzip" inside, log out, and systemctl stop inetd > kills screen, the shell inside, gzip etc. Yes, this is the whole point of KillMode=control-group. But how do you start from inetd and then get a shell? Are you starting sshd from inetd? It looks like your setup is a bit unusual, since nobody has noticed this since before jessie was released. -- ciao, Marco
signature.asc
Description: PGP signature
