<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - systemd-journald - 60 second pause in dracut, then systemd hangs at Init Default Target" href="https://bugs.freedesktop.org/show_bug.cgi?id=71721#c2">Comment # 2</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - systemd-journald - 60 second pause in dracut, then systemd hangs at Init Default Target" href="https://bugs.freedesktop.org/show_bug.cgi?id=71721">bug 71721</a> from <a class="email" href="mailto:james@nurealm.net" title="James <james@nurealm.net>"> James</a> <pre>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?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>