On Sat, Oct 11, 2014 at 06:33:39PM -0700, Russ Allbery wrote: > Christoph Anton Mitterer <[email protected]> writes: > > 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... > > 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.
Amen. 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 [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: https://lists.debian.org/[email protected]
