Am 17.05.2018 um 22:54 schrieb Igor Bukanov: > On 17 May 2018 at 19:23, Lennart Poettering <lennart at poettering.net> wrote: > >> So yes, this is a bug in nginx. They really should fix that. And this >> is not only broken when you use systemd, but on sysvinit too, as a >> command like this would likely fail there too: "service nginx start >> service nginx status", as the start would return before the PID file >> is written, and then status would claim the service to be down... > > Given that systemd deals with this situation in a very reasonable way, > nginx must not be alone in doing this. And if this a common way to > write such code, perhaps it should not be considered a bug but rather > one more peculiarity of application services the service manager > should deal.... why? either fix the pidfile stuff in nginx or simply start supporting "Type=notify" as a lot of other services already do and NO i don't grasp why "live updates" need that at all instead have main-pid as a tiny shim-controller which *never* exits at all