On Thu, Jun 07, 2018 at 07:32:10PM +0300, Mantas Mikulėnas wrote:
> On Thu, Jun 7, 2018 at 4:21 AM Chris Murphy wrote:
>
> > [chris@f28h ~]$ sudo journalctl --verify
> > 15f1c8: Data object references invalid entry at 4855f8
> > File corruption detected at
> > /run/log/journal/bbe68372db9f4c589a1
On Thu, Jun 7, 2018 at 4:21 AM Chris Murphy wrote:
> [chris@f28h ~]$ sudo journalctl --verify
> 15f1c8: Data object references invalid entry at 4855f8
> File corruption detected at
> /run/log/journal/bbe68372db9f4c589a1f67f008e70864/system.journal:4854c0
> (of 8388608 bytes, 56%).
> FAIL: /run/lo
On 7 June 2018 at 10:35, Lennart Poettering wrote:
> Nah, daemon() does not write PID files, you have to do that in your
> own code.
As daemon() calls _exit() (not even exit()) in the parent after the
fork, the only way to synchronize the pid writing is not to use the
daemon() at all and inline d
On Do, 07.06.18 09:50, Igor Bukanov (i...@mir2.org) wrote:
> On 18 May 2018 at 19:37, Lennart Poettering wrote:
> > On Do, 17.05.18 22:54, Igor Bukanov (i...@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.
> >
>
On Thu, 7 Jun 2018, Igor Bukanov wrote:
> On 18 May 2018 at 19:37, Lennart Poettering wrote:
> > On Do, 17.05.18 22:54, Igor Bukanov (i...@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 be
On 18 May 2018 at 19:37, Lennart Poettering wrote:
> On Do, 17.05.18 22:54, Igor Bukanov (i...@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
> nowa