/var/log/boot.log

jhwilliams · 09-13-2007, 12:27 PM

In fedora, /var/log/boot.log is an empty file and it is a known bug. Is there anyway go get around this? What causes it, and what I can do to help fix the problem? It is a serious inconvenience if you even think about touching the kernel.

unSpawn · 09-13-2007, 03:32 PM

Add line "local7.* /var/log/boot.log" (check tab usage) to /etc/syslog.conf then kill -HUP syslogd?

jhwilliams · 09-13-2007, 03:46 PM

syslogd's conf file has that already, at the bottom. the kill -hup deal happens (implicitly) when i restart my system each time. :-( any other ideas?

unSpawn · 09-13-2007, 03:55 PM

Quote:

Originally Posted by jhwilliams

it is a known bug.

Aww, sorry. I read over that. What's the bugtracker ID (in the hope it at least has a rudimentary description)?

jhwilliams · 09-13-2007, 04:31 PM

Quote:

Originally Posted by unSpawn

What's the bugtracker ID (in the hope it at least has a rudimentary description)?

Good point. The bug ID is 163461, although the thread there is fairly inconclusive and depressing. Looks like CentOS and RHEL got this bug, too.

unSpawn · 09-13-2007, 05:15 PM

OK. Thanks for posting the ID. It shows only one "alternative" (using 'logger'). But how about retrofitting minilogd and initlog?