On Thu, 2018-04-12 at 09:35 +0000, dave_horton2...@hotmail.com wrote: > I have a service on my 389-ds host that is configured in systemd to > depend on 389-ds and start after dirsrv.target. However, unless I > add a sleep (ExecStartPre systemd stanza) to the startup of that > other service it fails to start as 389 is not fully ready. I can see > that systemd is respecting the dependencies, but the client starts > before 389 is able to accept its connection. > > 389-ds appears to use the notify systemd service type. Is it > possible that sd_notify is being called before the services are truly > ready to accept client connections?
sd_notify is called just before the event loop wait starts. I don't think it's possible for this to be incorrect. The only thing I can assume is that there is some other systemd weirdness here, but the design of what's in 389 is correct to my knowledge. If you want I can send you all the details needed to audit this if you want :) Sorry I can't help more :( William > _______________________________________________ > 389-users mailing list -- email@example.com > To unsubscribe send an email to firstname.lastname@example.org > rg _______________________________________________ 389-users mailing list -- email@example.com To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org