On Sun, Oct 12, 2014 at 04:12:07AM +0200, Christoph Anton Mitterer wrote: > 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. =)
That would be the systemd way to do it and instantly spawn a new hate wave. After all, it was systemd locking people out of their headless, remote systems during an urgent security update. Don't change this behavior. Please. Greetings Marc -- ----------------------------------------------------------------------------- Marc Haber | "I don't trust Computers. They | Mailadresse im Header Leimen, Germany | lose things." Winona Ryder | Fon: *49 6224 1600402 Nordisch by Nature | How to make an American Quilt | Fax: *49 6224 1600420 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
