https://bugzilla.mindrot.org/show_bug.cgi?id=2641
Petr Cerny [:hrosik] <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #12 from Petr Cerny [:hrosik] <[email protected]> --- (In reply to Damien Miller from comment #11) > I don't understand the problem here. > > Can you not arrange for systemd to run sshd with the -D flag to > begin with? When sshd restarts for SIGHUP it will reexec itself with > the same commandline argument and will therefore not daemonise. That is an option, yet it has other drawbacks and one needs to carefully step among all the combinations that have some kind of race condition or similar problems (those were actually the reason for the Debian/RH/SUSE issues referenced above). That said, putting in an ifdeffed init system integration doesn't need to be a bad idea (I intentionally avoided writing 'systemd', as I personally consider this to be a broader issue, which would be present with any other init system that would want to keep track of the state the services are in.) Would it help if the state reporting was init-system agnostic - say split into a separate file(s) the way auditing is? (From my point of view that would be the right thing.) -- You are receiving this mail because: You are watching the assignee of the bug. You are watching someone on the CC list of the bug. _______________________________________________ openssh-bugs mailing list [email protected] https://lists.mindrot.org/mailman/listinfo/openssh-bugs
