Bug#751636: openssh-server: ssh sessions are not cleanly termined on shutdown/restart with systemd
On Fri, Oct 10, 2014 at 05:44:14PM +0200, Christoph Anton Mitterer wrote:
> a) if sshd crashes or when it is restarted/reloaded (or when the network
> is restarted), we do not want ssh sessions to terminate, right?
At least that's what we always had. I would like to have a method to
kill all ssh sessions with the exception of my own ones, or the single
session that I happen to type the command restarting sshd in.
> b) we want a way to actually stop user sessions... not only for this
> particular bug (i.e. on shutdown), but as a locally logged in sysadmin
> I'd also like to say "okay... away with sshd and it's users".
Agreed. We didn't have that until jessie though.
> AFAICS, this should solve (a) and (b), the only difference to now would
> be, that we need to educate our users/admins, that "systemctl stop ssh"
> really means "all ssh stops" and not just "the main ssh daemon stops but
> old connections remain".
That would be a pretty severe change from the behavior we used to have
for fifteen years. I also guess it would be used as an argument
against systemd as a whole.
Please consider not changing this behavior to keep system acceptance up.
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
Reply to: