Hello, On Thu, Aug 23, 2018 at 4:53 PM kevin martin <ktmdms@xxxxxxxxx> wrote: > > I'm not sure I agree with Peter in respect to his comment about "building a > dependency to systemd". The only time a "dependency" would be created is > when the end-user would configure it to be there with a configure time flag > of --with-systemd. Just having the code available and dormant without that > flag being provided builds in no dependency whatsoever and gives the > end-user their option to choose. Not sure I should step in, but the code to deal with the user selection and to notify systemd is a dependency - even if it's compiled out. The fact is that you still ave to maintain it and to test it regularly. The problem looks like a systemd configuration error. systemd allows you to start a non-systemd-aware daemon. You need to look at [Service] / Type (notify is used for systemd-aware daemons). BR, -- Emmanuel Deloget _______________________________________________ openssh-unix-dev mailing list openssh-unix-dev@xxxxxxxxxxx https://lists.mindrot.org/mailman/listinfo/openssh-unix-dev