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) So where in a pre-journald world I'd have found everything till the crash in /var/log messages (possibly, with some corrupted lines in the middle I would just ignore), in a journald world there is a whole blackhole right where the incident occurred, and the data is not parsed by journald nor relayed to syslog. This is seriously underwhelming. -- Nicolas Mailhot -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
