On Wed, Feb 12, 2014 at 01:15:39AM +0200, Uoti Urpala wrote: > On Tue, 2014-02-11 at 21:52 +0000, Colin Watson wrote: > > OK. I've pushed this commit: > > > > > > http://anonscm.debian.org/gitweb/?p=pkg-ssh/openssh.git;a=commitdiff;h=a92ab9ee301bc9196bb20f4923886f021f070521 > > > > Let me know if that still looks wonky. > > The description itself looks OK, but I think a section title like > "per-connection sshd instances" (or "per-connection sshd instances under > systemd" if you want to emphasize the description only works under > systemd) would be preferable to the current "systemd socket activation".
Yeah, never try to write documentation while talking to people in real life at the same time ... fixed, thanks. > At least a script from another package could trigger a daemon-reload > call between unpacking openssh-server and configuring it. So the system > could at least be in a somewhat inconsistent state between that and the > start-stop-daemon call. However, when writing the above I was somehow > confused between start-stop-daemon and invoke-rc.d - raw > start-stop-daemon should work regardless of the confused state. The > problem preventing it from being stopped is likely a simple incorrect > negation in the postinst: the stop call is under "! systemctl --quiet > is-active ssh" - only stopping it if it's already NOT active. That was intentional; if the sysvinit-started sshd is still running, then it will surely not be active as far as systemd is concerned. I didn't want to mess about with start-stop-daemon if systemd had already taken control of it. Did you manage to find those logs? -- Colin Watson [[email protected]] -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
