Re: [systemd-devel] How to guarantee the stdout buffer between systemd and journald is flushed when program quits?

2018-05-18 Thread Ivan Kurnosov
I'm observing it on the ubuntu bionic that comes with systemd 237 On 19 May 2018 at 07:27, Lennart Poettering wrote: > On Fr, 18.05.18 09:02, Ivan Kurnosov (zer...@zerkms.ru) wrote: > > > Hi, > > > > I originally asked this question on the stackoverflow ( > > https://stackoverflow.com/q/50400145

Re: [systemd-devel] How to guarantee the stdout buffer between systemd and journald is flushed when program quits?

2018-05-18 Thread Lennart Poettering
On Fr, 18.05.18 09:02, Ivan Kurnosov (zer...@zerkms.ru) wrote: > Hi, > > I originally asked this question on the stackoverflow ( > https://stackoverflow.com/q/50400145/251311) but I feel I wouldn't get an > answer there. > > The simplified example that demonstrates a problem is > > #include

Re: [systemd-devel] option to wait for pid file to appear

2018-05-18 Thread Lennart Poettering
On Do, 17.05.18 22:54, Igor Bukanov (i...@mir2.org) wrote: > On 17 May 2018 at 19:23, Lennart Poettering 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 fa

Re: [systemd-devel] option to wait for pid file to appear

2018-05-18 Thread Ian Pilcher
On 05/17/2018 03:54 PM, Igor Bukanov wrote: 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