On Mon, Nov 25, 2013 at 12:58 AM, Frantisek Hanzlik <franta(a)hanzlici.cz> wrote:
Frank Murphy wrote:
> On Sun, 17 Nov 2013 12:37:03 +0100
> Patrick Lists <fedora-list(a)puzzled.xs4all.nl> wrote:
>>
>> I meant the transmission of the log to another log server. Not the
>> log itself. Anyway, here is Lennart Poettering's rationale behind
>> journald:
>
> One of the things you will see after a hard reset is:
> Journal corrupted, journal deleted and being restarted.
> ie.. no useful info.
This is perhaps most significant shortcoming. And beside it I see in
log messages as:
systemd-journald[295]: Failed to set ACL on
/var/log/journal/70ed4dbe694041d484165719514f195e/user-1045.journal, ignoring: Invalid
argument
systemd-journald[2948]: Failed to write entry, ignoring: Cannot allocate memory
systemd-journal[388]: Suppressed 966 messages from /system/dbus.service
systemd-journal[299]: Forwarding to syslog missed 92 messages.
which induce sense of journald logging futility.
Googling shows that it was fixed in May and applied in OpenSUSE in
June and in Debian in September:
http://lists.opensuse.org/opensuse-commit/2013-06/msg01102.html
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717863
Given that there have been F19 systemd uploads since May, I assume
that it's also fixed in Fedora but the changelogs don't mention it.