On 18 May 2018 at 19:37, Lennart Poettering <lennart at poettering.net> wrote: > On Do, 17.05.18 22:54, Igor Bukanov (igor at mir2.org) wrote: > Well, no. The protocol is clear, and what we do is pretty close to > black magic, and still racy in many ways. > > I mean, broken behaviour is still broken behaviour, even if we > nowadays handle it pretty nicely. Really, nginx should be fixed, > everybody benefits, sysvinit as much as we do. It turned out it is not only nginx that behaves this way. Any program that is using the daemon(3) call available both in Linux and BSD writes the pid from the child without the parent waiting. So this behaviour must be widespread and as such I think must be accepted as a de-facto standard (even if it is unfortunate) and systemd should not even warn about it.