Description of problem:
Unable too boot is LogTarget in /etc/systemd/system.conf is set to syslog-or-kmsg or syslog.
Version-Release number of selected component (if applicable):
Change LogTarget in /etc/systemd/system.conf to syslog-or-kmsg or syslog and reboot.
System cannot boot.
System boot normally.
I know systemd is really BAD (use-it since it was introduced to Fedora) but since is "community" linux I can more ol less accept-it like it is. But you people made-it even worse in RHEL7!
Thanks for the bug report, we always appreciate constructive criticism. We need to backport http://cgit.freedesktop.org/systemd/systemd-stable/commit/?id=b7f2e5ac769ca4d9b7d28050ec662104635a7822
> If journald cannot process a message from PID1 for 10 ms then something is
> significantly wrong. It's better to lose the message and continue.
Really? Lose the message? That's the best systemd can do?
In PID the effective difference between "syslog" and "journal" is pretty minimal. We should probably stop documenting "syslog" and just implicitly turn all "syslog" log targets into "journal".
Ok, dropping log messages even just from systemd itself isn't probaly a best way, but wee need more time for investigation.
This should be now fixed with the rebase.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.