Re:Re: [gentoo-user] systemd-journald: user-1000.journal ... Not a XENIX named type file
No. I suspect that the battery on the mainboard is too old to keep the clock working on the mainboard. But the time of the boot shown on the screen is later than the last boot, and the time after my login is a little later than the previous journal file. Does it matter to keep the clock exact? I always think that the boot time later than the previous shutdown time is just OK. At 2023-02-26 10:57:37, "Matt Connell" wrote: >On Sun, 2023-02-26 at 10:31 +0800, johnstrass wrote: >> Monotonic clock jumped backwards relative last journal entry > >Is your system clock accurate? Is it in sync the the hardware clock, >if the machine has one? >
Re: [gentoo-user] systemd-journald: user-1000.journal ... Not a XENIX named type file
On Sun, 2023-02-26 at 10:31 +0800, johnstrass wrote: > Monotonic clock jumped backwards relative last journal entry Is your system clock accurate? Is it in sync the the hardware clock, if the machine has one?
[gentoo-user] systemd-journald: user-1000.journal ... Not a XENIX named type file
Hi there, I am using a Loongson2f Yeeloong netbook and have upgraded to kernel 6.0.5. When I boot and login after typing the password, systemd-journald shows: systemd-journald [144]:/var/log/journal/67er8fc429e5364af4fe1074626r7e38/user-1000.journal: Monotonic clock jumped backwards relative last journal entry, rotating. systemd-journald[144]: Failed to write entry to /var/log/jourmal/67er8fc429e5364af4fe1074626r7e38/user-1000.journal (30 items, 791 bytes ), rotating before retrying : not a XENIX named type file Is this a serious problem? What can I do to avoid this? Thanks.
