Le Mar 16 juillet 2013 13:25, Lennart Poettering a écrit : > On Tue, 16.07.13 11:37, Nicolas Mailhot (nicolas.mail...@laposte.net) > wrote: > >> >> Le Lun 15 juillet 2013 15:47, Lennart Poettering a écrit : >> >> > There's the general problem that once /var is read-only we cannot >> really >> > store logs anywhere anymore that survive the reboot. On our TODO list >> is >> > to optionally store all logs generated beyond that point in some UEFI >> > variable, and collect it on next boot. >> >> BTW another case I've seen where systemd disappointed be, that's when in >> case of problem, instead of trying to salvage logs at the next boot, it >> just considers the log file corrupted and ignores it. (there was a >> useless >> message about it, I have zero wish to try to salvage a binary data file >> manually) > > I am pretty sure that is just a misunderstanding.
I certainly hope so :) > So yeah, you could say that journald will 'ignore' the file. But > journalctl won't, it will show them to you. And that's *good* that > way. That's how it *should* be. However even if that's the case that means some events just got hidden in a file only journalctl will consult, and not relayed to syslog (as they should) -- Nicolas Mailhot -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
