Empty boot.log

[Erik P. Olsen]

On 11/10/09 00:32, Giovanni P. Tirloni wrote:
> 
> 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

[root at epotest ~]# ps ax|grep plymouth
 1840 pts/0    S+     0:00 grep plymouth

[root at epotest ~]# ps axZ|grep plymouth
unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 1842 pts/0 S+   0:00
grep plymouth

[root at epotest ~]# ls -lZ /var/log/boot.log
-rw-------. root root system_u:object_r:var_log_t:s0   /var/log/boot.log

[root at epotest ~]# grep local7 /etc/rsyslog.conf
local7.*                                                   /var/log/boot.log

-- 
Cheers
Erik.