openssh 7.6 and 7.7 on Oracle Linux 7 (compiled from source) doesn't start correctly with systemd

kevin martin ktmdms at gmail.com
Thu Aug 23 01:53:35 AEST 2018


yep, that race condition is exactly what i was experiencing.  I'm not sure
why having the systemd notify code in openssh as a configure time option
would be such a bad thing.

---


Regards,

Kevin Martin


On Wed, Aug 22, 2018 at 10:45 AM Jakub Jelen <jjelen at redhat.com> wrote:

> On Wed, 2018-08-22 at 09:02 -0500, kevin martin wrote:
> > Simple seems to have fixed it.  I was also trying with "forking" as
> > the
> > type and that was failing as well.
>
> That is not as simple as that -- we lived with "simple" for long time,
> but it was not covering some corner cases so we ended up using the
> sd_notify, since that was the only reliable way for systemd to know the
> service is working.
>
> For others interested in this topic, there was a long discussion in bug
> #2641, unfortunately without upstream solution:
>
> https://bugzilla.mindrot.org/show_bug.cgi?id=2641
>
> Regards,
> --
> Jakub Jelen
> Software Engineer
> Security Technologies
> Red Hat, Inc.
>
>


More information about the openssh-unix-dev mailing list