Description of problem: I had to relabel for SELinux by creating /.autorelabel and rebooting. During the relabeling process the message "Starting systemd Syslog Kernel Log Buffer Bridge" repeated at least a dozen times. I assumed thad during relabeling nothing else should run? And why repeat the same message a lot? Version-Release number of selected component (if applicable): systemd-18-1.fc16.x86_64 policycoreutils-2.0.85-12.fc15.x86_64 How reproducible: No idea, happened once Steps to Reproduce: 1. Create /.autorelabel, reboot 2. 3. Actual results: Lots of "Starting ..." messages during relabeling Expected results: There should be minimal activity during relabeling. Additional info:
That's a tiny bridge that connects /dev/log to kmsg. It is only started when some process writes something to /dev/log, and then terminates itself automatically after 10s (as a side note: I inreased that to 5min in systemd git). So, this is not really systemd's fault: something is writing messages to /dev/log. And we shouldn't make systemd ignore that but figure out what exactly is responsible for that. Any chance you could try to reproduce this issue but boot with plymouth completely off ("rd_NO_PLYMOUTH" on the kernel cmdline) and with debug output of the kernel on? ("debug" on the kernel cmdline). Then, the messages written to /dev/log should reach the console via kmsg, and we should be able to figure out what is going on.
*** Bug 669692 has been marked as a duplicate of this bug. ***
This has been fixed (just had to relabel because of /run, no trouble whatsoever). Can't say which of the hundreds of updates did the trick :-(
OK, thanks. Closing then.