[systemd-bugs] [Bug 71721] systemd-journald - 60 second pause in dracut, then systemd hangs at Init Default Target

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=71721

--- Comment #2 from James <james at nurealm.net> ---
Yes, for either "debug" and no other specific log option, or for an explicit
"systemd.log_target=kmsg", there is no blocking and no hang, and operation
seems normal.

So that works, except that it creates a "Heisenbug", where, like some "quantum
event", the problem goes away when you try to observe it, with "debug".

If you want to do this kind of modified behavior with "debug", there should at
least be very profuse and verbose and loud disclosure in the system log, saying
that the underlying systemd behavior has been modified, and that the logging
has been automatically - and not "silently" - changed, from "journal logging"
to "kernel logging", and that "journal blocking behavior" will disappear as a
result of this change.  Otherwise, systemd is going to be very mysterious and
"un-discoverable", and debugging is going to be a PITA.

In the long run, it would seem to me, that "journal blocking" is not
appropriate behavior.  Instead, perhaps, systemd-journald should throw a very
loud warning message, and then continue.  Wasn't that the whole point of
setting-up sockets with systemd, not slowing the boot process, because of any
one misbehaving process?

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-bugs/attachments/20131118/1543da58/attachment.html>