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 that: * openssh-server comes configured _out of the box_ with UsePAM=yes enabled * Openssh-server's installation default is as a systemd service * libpam-systemd adds functionality to openssh-server in that connections are properly terminated upon shutdown (while the ‘maintain connections’ behavior if the sshd process is stopped/restarted is preserved) * There is no mention of the package libpam-systemd as being related in any way at all to openssh-server on https://packages.debian.org/jessie/openssh-server (rec/sug/enh, much less as a hard dependency) …My feeling is, I’d construe THAT to be the real bug here. I don’t know enough about debian’s package relationships to say what relationship libpam-systemd should have to openssh-server, but I’m pretty sure that ‘none whatsoever’ is not the answer. Similarly, > > I still see the issue from time to time, even though I have PAM > > enabled. > > > > E.g. just a few minutes ago it happened again with: > > # 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). Exiting. > > <here it hangs> As suggested in the serverfault answer, and possibly by the above error, does dbus need a relationship either to systemd or openssh-server? ArchLinux and FedoraCore both list dbus as a _requirement_ for systemd. Debian does not AFAICT, and I’m wondering if that should change. [Yes, this is me saying ‘Others do it, why don’t we?’, but I think it’s a fair question to ask here. If dbus would provide information to systemd to manage openssh-server client connections more effectively, shouldn’t it be a dependency to one or the other?] Best, R.S. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
