[systemd-devel] Journald : from initialramfs to real root

Mantas Mikulėnas grawity at gmail.com
Tue Feb 25 18:49:08 UTC 2025


On Tue, Feb 25, 2025 at 8:13 PM Thomas HUMMEL <thomas.hummel at pasteur.fr>
wrote:

> On 2/25/25 6:57 AM, Mantas Mikulėnas wrote:
>
> Hello,
>
> thanks for your answer.
>
> > These seem like rsyslogd has picked them up directly from the kernel
> (from
> > the legacy /proc/kmsg guessing from the format) and not from the journal.
> > Systemd-journald loads kernel logs via /dev/kmsg which wouldn't have the
> > [time.stamp] prefix.
>
> hmmm not sure how it's supposed to work. I assume both refer to the same
> ring buffer. Would a reader consume what it reads which would then not
> be in the buffer anymore for the second reader to read ? If so wouldn't
> that be journald first ?
>

Reading from /dev/kmsg doesn't consume the buffer.


> > I believe it just logs to /run/log
>
> But this seems to go against the fact that intitalramfs journald can
> show intitialramfs systemd units (which dracut services are) logs, no ?


No, why do you think so?

-- 
Mantas Mikulėnas
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/systemd-devel/attachments/20250225/4e60482a/attachment.htm>


More information about the systemd-devel mailing list