Bug#751636: ssh sessions are not cleanly terminated on shutdown/restart with systemd

On Sun, 7 Feb 2016 14:36:24 +0100 "Alexander Afonyashin" wrote: > 1. Remove symlink /etc/systemd/system/sshd.service -> > /lib/systemd/system/ssh.service - who knows what does symlink do here? > 2. Copy /lib/systemd/system/ssh.service to /etc/systemd/system/ssh.service. Forking

Bug#751636: ssh sessions are not cleanly terminated on shutdown/restart with systemd

Hi, Small update to previous letter: it's better to replace 'killall sshd' with 'pkill sshd' as psmisc package isn't installed by default if no packages were selected during setup. So ExecStop should be: ExecStop=/usr/bin/pkill sshd   Best regards, Alexander Afonyashin

Bug#751636: ssh sessions are not cleanly terminated on shutdown/restart with systemd

Hi,   The following works for me on Debian 8.3:   1. Remove symlink /etc/systemd/system/sshd.service -> /lib/systemd/system/ssh.service - who knows what does symlink do here? 2. Copy /lib/systemd/system/ssh.service to /etc/systemd/system/ssh.service. 3. Edit /etc/systemd/system/ssh.service,

Bug#751636: ssh sessions are not cleanly terminated on shutdown/restart with systemd

Hi,   The following works for me on Debian 8.3:   1. Remove symlink /etc/systemd/system/sshd.service -> /lib/systemd/system/ssh.service - who knows what does symlink do here? 2. Copy /lib/systemd/system/ssh.service to /etc/systemd/system/ssh.service. 3. Edit /etc/systemd/system/ssh.service, add

Bug#751636: ssh sessions are not cleanly terminated on shutdown/restart with systemd

It's very surprising that this bug hasn't been addressed for more than a year. This ssh connection hangup never happens under FreeBSD, for instance. systemd may just be too buggy, since it has another design deficiency, namely being unable to save system time upon reboots (along the lines of

Bug#751636: ssh sessions are not cleanly terminated on shutdown/restart with systemd

On Sun, 2015-09-20 at 12:42 +0500, rihad wrote: > systemd may just be too buggy, since it has another design > deficiency This isn't a bug in systemd... o.O smime.p7s Description: S/MIME cryptographic signature

Bug#751636: ssh sessions are not cleanly terminated on shutdown/restart with systemd

I found a serverfault answer that led me down the path of reasoning below. Have a look: http://serverfault.com/a/706494 If sshd is configured with UsePAM yes, then after installing libpam -systemd to a remote system and rebooting, ssh sessions are cleanly terminated… Given the above and

Bug#751636: ssh sessions are not cleanly terminated on shutdown/restart with systemd

Well,... By chance, I just had it again: # reboot PolicyKit daemon disconnected from the bus. We are no longer a registered authentication agent. g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0).

Bug#751636: ssh sessions are not cleanly terminated on shutdown/restart with systemd

On 07/06/2015 08:09 AM, Christoph Anton Mitterer wrote: On Sat, 2015-07-04 at 14:40 -0700, Daniel Kauffman wrote: If sshd is configured with UsePAM yes, then after installing libpam -systemd to a remote system and rebooting, ssh sessions are cleanly terminated, but after purging libpam-systemd

Bug#751636: ssh sessions are not cleanly terminated on shutdown/restart with systemd

On Sat, 2015-07-04 at 14:40 -0700, Daniel Kauffman wrote: If sshd is configured with UsePAM yes, then after installing libpam -systemd to a remote system and rebooting, ssh sessions are cleanly terminated, but after purging libpam-systemd and rebooting, ssh session are not cleanly

Bug#751636: ssh sessions are not cleanly terminated on shutdown/restart with systemd

If sshd is configured with UsePAM yes, then after installing libpam-systemd to a remote system and rebooting, ssh sessions are cleanly terminated, but after purging libpam-systemd and rebooting, ssh session are not cleanly terminated. If sshd is configured with UsePAM no, then