On Sat, Oct 11, 2014 at 08:12:56PM -0700, Russ Allbery wrote: > I have no problems with the current behavior under systemd, so I'm not the > one to ask for a solution. It makes no difference at all to me whether I > get a clean connection shutdown from a host when it's being rebooted.
It makes a big difference to me when working with multiple hosts at once. I will only get back my shell after a manual action or after waiting for the host to return to the network to finally send an RST. > That didn't reliably happen even under sysvinit-started sshd. It happened reliably in so many cases that I don't even remember the last time where a sysvinit system didn't return me cleanly and quickly to my shell on shutdown. It was a big WTF when my first systemd system behaved that way. If sysvinit were so unreliable in its behavior on shutdown, I would have been at least a bit familiar with the "new" behavior, and I do not like it at all. This change will not improve systemd's behavior, as it is one more place where the self-proclaimed "drop-in replacement to sysvinit" changes system behavior in a _very_ prominent way. > If you can find a way to improve the behavior along some axis that you > care about, I'm certainly fine with that, but given that I don't even > consider the problem that you're trying to solve to be a problem, I'm > going to have a low tolerance for regressions. :) jftr, I see the changed behavior as a problem. 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]
