Re: Empty boot.log

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




On Oct 10, 2009, at 6:18 PM, Erik P. Olsen wrote:

On 10/10/09 20:09, Giovanni P. Tirloni wrote:

Plymouth is the component responsible for recording those messages in
/var/log/boot.log when the root fs becomes writeable. You should check
if plymouthd is running.

How do I check if plymouthd is running when I don't see the boot messages
and boot.log is empty?

# ps ax | grep plymouth
  105 ?        S      0:02 /bin/plymouthd --attach-to-session

# ps axZ | grep plymouth
system_u:system_r:kernel_t:s0 105 ? S 0:02 /bin/ plymouthd --attach-to-session

# ls -lZ /var/log/boot.log
-rw-r--r--. root root system_u:object_r:var_log_t:s0   boot.log


Are all the other log files in /var/log working fine ? Your rsyslog.conf should have a line like this:

# grep local7 /etc/rsyslog.conf
local7.* /var/log/ boot.log


-Giovanni




--
fedora-test-list mailing list
fedora-test-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list

[Index of Archives]     [Fedora Desktop]     [Fedora SELinux]     [Photo Sharing]     [Yosemite Forum]     [KDE Users]

  Powered by Linux