On Fr, 29.01.21 11:34, John Lane (syst...@jelmail.com) wrote:
> >
> > Is it possible you are playing some weird games with your machine ID
> > or boot ID?
> >
>
> Maybe. Yes. I have a oneshot service that writes /etc/machine-id using
> constant hardware-based info. But I've been using that for
>
> Is it possible you are playing some weird games with your machine ID
> or boot ID?
>
Maybe. Yes. I have a oneshot service that writes /etc/machine-id using
constant hardware-based info. But I've been using that for over two
years without any issues.
I did notice this when trying to
On Do, 28.01.21 17:42, John Lane (syst...@jelmail.com) wrote:
>
>
> > journalctl reads from both dirs, always. What makes you think it reads
> > from the wrong dir only?
> >
>
> when I do `journalctl` I only get output up to the switch-root:
>
>
> Jan 28 08:33:31 archlinux systemd[1]: Reached
> journalctl reads from both dirs, always. What makes you think it reads
> from the wrong dir only?
>
when I do `journalctl` I only get output up to the switch-root:
Jan 28 08:33:31 archlinux systemd[1]: Reached target Switch Root.
Jan 28 08:33:31 archlinux systemd[1]: Starting Switch
On Fr, 15.01.21 09:17, John Lane (syst...@jelmail.com) wrote:
> Hello,
>
> I've just set up a new system and have noticed a problem with journalctl
> where it appears to be reading from the incorrect journal. The journal
> is running and I can direct it at the correct file using -D, but I don't
>
I'm still stuck on this one, if anyone can offer any advice I'd really
appreciate it as I'm not sure how to troubleshoot it.
On 15/01/2021 09:17, John Lane wrote:
> Hello,
>
> I've just set up a new system and have noticed a problem with journalctl
> where it appears to be reading from the
Hello,
I've just set up a new system and have noticed a problem with journalctl
where it appears to be reading from the incorrect journal. The journal
is running and I can direct it at the correct file using -D, but I don't
understand what is happening.
There is a journal in /run/log/journal
