journal: don't log to console AND kmsg #19
Conversation
dustymabe
changed the title
If we do that then we get "double logs" on the console device because both kmsg and console output is getting dumped there.
|
cc @lucab |
|
This looks like the third back-and-forth on those options, and unfortunately I miss context to know what's going on. If we are only concerned with a single service (Ignition stages), we can directly tweak those instead of affecting the whole journald: https://www.freedesktop.org/software/systemd/man/systemd.exec.html#StandardOutput= |
|
Today we have what we want, except we get double messages on the primary console= device. My personal preference is that we want all systemd logs to be spit out during the initramfs, which is why I prefer it to be in the journald.conf rather than in the individual unit files. see also dracutdevs/dracut#445 |
|
Ack, then let's tentatively land this and re-check that the double console-output disappeared and nothing else regressed, in the next pipeline run. |
if we do that then we get "double logs" on the console device
because both kmsg and console output is getting dumped there.