On Sat, 2014-10-11 at 18:33 -0700, Russ Allbery wrote: > Yes, a lot of people being *quite* upset when they stop ssh to restart it > with debugging or to temporarily bring it down while working on something, > discover that their session was terminated in a way that's never happened > with ssh in the past, and now be unable to connect to the system since it > was a remote server. > > Let's not do that. That would be really unpleasant. We need to preserve > the current sshd behavior that stopping the service does *not* kill open > sessions. Well never too late to change something *if* it was the cleaner way to handle it. =) Anyway,... what would you propose then to bring everything under one hat? 2 service files? Or even three? Like ssh.service sshd.service ssh-sessions.service with: - sshd.service being the daemon, that, if stopped/restarted, leaves ssh-sessions.service alone - ssh-session.service being the one that stops the ssh sessions (either manually, when the admin wants it, or on shutdown) - and ssh.service being simply something that depends on both (i.e. stops both and starts sshd.serice) ? Cheers, Chris.
Attachment:
smime.p7s
Description: S/MIME cryptographic signature