On Sat, 2014-10-11 at 11:23 +0200, Tom Hutter wrote: > Exactly. Stop apache, nginx, mysql, postgres and tell me, how many > children processes will be left, once you stopped it. > > As ssh behaves differently and keeps the children alive, you have to > handle it differently :-) Sure... But I mean before thinking about "how to handle it technically",... it should probably decided "what do we actually want". Like "even if ssh itself (the binary) behaves different from apache/etc. - do we want to keep that in the unit-files or do we want "stop" to generally mean that everything from that service is stopped". I personally would tend to the later, though this may have many implications... And when you're right, that systemd restart == stop + start... then this would be anyway difficult. > systemctl stop ssh.service => all existing user sessions will stay > alive Sure, I know,... due to the KillMode=process Cheers, Chris.
Attachment:
smime.p7s
Description: S/MIME cryptographic signature