The local7 facility is used to write into the /var/log/boot.log file.
But since the Fedora core 4, the system has been disabled waiting for a new generation system which does not seem to be available yet (see this bug report and this one)
A quick way to fix the empty /var/log/boot.log file, is to edit the /etc/rc.d/init.d/functions file.
Into the success, failure, passed and warning functions, you can add a line like the following, just before the return instruction:
/usr/bin/logger -p local7.info "$1"
It works but each time the initscripts package is updated, it is needed to edit the file ...
sharing knowledge earned into design/development/technical delicate and/or difficult situations ...
Labels
Gnu/Linux
(95)
Administration
(83)
StorageHardware
(17)
Programming
(16)
WebBrowser
(15)
General
(11)
GNU/Bash
(7)
Solaris
(7)
Virtualization
(7)
C
(6)
Domotics
(6)
Musics
(5)
Raspberry
(5)
Desktop
(4)
Java
(4)
VersionControlSystems
(4)
ArtificialIntelligence
(2)
Optimization
(2)
multimedia
(2)
Arduino
(1)
Electronics
(1)
LTS
(1)
MacOS
(1)
Mechanics
(1)
Processing
(1)
Robotics
(1)
Ubuntu
(1)
Upgrade
(1)
ez-robot
(1)
Good job and thank you.
ReplyDeleteThere is not as much info. in boot.log as I thought there would be. CentOS 5.x (basically Redhat) had an Error Log available in the menu under Applications - System Tools - System Logs. Fedora 9 only provides Cups Errors. Do you know anything about enabling system wide, or boot error logging in Fedora 9?
Thanks again, Tim
Thanks tim valentine.
ReplyDeleteUnfortunately, I do not know anything else yet to get more information.
As soon as I found a solution, I'll post another message and inform you.
I will check back from time to time in case you find a solution. I have no further information regarding this topic either.
ReplyDelete