Pekka Paalanen writes:
> have you checked your boot ID, maybe it's often the same as the previous
> boot?
Good thought, but it doesn't look like it:
IDX BOOT ID FIRST ENTRY LAST ENTRY
-20 c2a5e3af1f044d79805c4fbdd120beec Wed 2023-05-10
On Thu, 05 Oct 2023 13:32:37 -0400
Phillip Susi wrote:
> Phillip Susi writes:
>
> > Lennart Poettering writes:
> >
> >> It actually checks that first:
> >>
> >> https://github.com/systemd/systemd/blob/main/src/libsystemd/sd-journal/journal-file.c#L2201
> >>
> >
> > That's what I'm
Phillip Susi writes:
> Lennart Poettering writes:
>
>> It actually checks that first:
>>
>> https://github.com/systemd/systemd/blob/main/src/libsystemd/sd-journal/journal-file.c#L2201
>
> That's what I'm saying: it should have noticed that FIRST and not gotten
> to the monotonic time check, but
Lennart Poettering writes:
> It actually checks that first:
>
> https://github.com/systemd/systemd/blob/main/src/libsystemd/sd-journal/journal-file.c#L2201
That's what I'm saying: it should have noticed that FIRST and not gotten
to the monotonic time check, but it didn't.
On Do, 25.05.23 14:32, Phillip Susi (ph...@thesusis.net) wrote:
>
> Lennart Poettering writes:
>
> > We want that within each file all records are strictly ordered by all
> > clocks, so that we can find specific entries via bisection.
>
> Why *all* clocks? Even if you want to search on the
Lennart Poettering writes:
> We want that within each file all records are strictly ordered by all
> clocks, so that we can find specific entries via bisection.
Why *all* clocks? Even if you want to search on the monotonic time, you
first have to specify a boot ID within which that monotonic
On Di, 23.05.23 11:04, Phillip Susi (ph...@thesusis.net) wrote:
> Every time I reboot, when I first log in, journald ( 253.3-r1 )
> complains that the monotonic time went backwards, rotating log file.
> This appears to happen because journal_file_append_entry_internal()
> wishes to enforce strict
Every time I reboot, when I first log in, journald ( 253.3-r1 )
complains that the monotonic time went backwards, rotating log file.
This appears to happen because journal_file_append_entry_internal()
wishes to enforce strict time ordering within the log file. I'm not
sure why it cares about the
