On Fri, Oct 10, 2014 at 10:51:04AM -0500, David Lechner wrote: > I have found that using ssh.socket instead of ssh.service makes > clients shut down cleanly most of the time (sometimes they will > still hang, but it is rare). > > systemctl disable ssh.service > systemctl enable ssh.socket
Do I understand correctly, that ssh in jessie/sid allows the local admin to run sshd as a traditional daemon, with the new (undesired) behavior, or as a systemd service with socket activation, which gives a better emulation of traditional behavior? If this is really seriously meant that way, people will see this as a conspiracy to coax people into using socket activation. Danger, Will Robinson. 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
