https://bugzilla.mindrot.org/show_bug.cgi?id=2641
--- Comment #4 from Jakub Jelen <jje...@redhat.com> --- Colin, the -D was omitted (and Type=Forking added) because systemd was unable to report failures (when configuration file had an error), as described in the Red Hat bugzilla [1]. Certainly, the -D makes more sense these days, but with that, typing systemctl restart sshd is not producing any error with -D option. Also no error goes into the journal (as in the description of the linked bug). The one solution is "letting that particular camel's nose into the tent" as used in Ubuntu/Debian, but I still hope, there is a better way to do that. Clearly, what I am trying to point out here is that the applied change is modifying the behavior not only for re-exec (reload), but also for the "start", which was not intentional to my understanding. [1] https://bugzilla.redhat.com/show_bug.cgi?id=1291172 -- You are receiving this mail because: You are watching someone on the CC list of the bug. You are watching the assignee of the bug. _______________________________________________ openssh-bugs mailing list openssh-bugs@mindrot.org https://lists.mindrot.org/mailman/listinfo/openssh-bugs
