FS#19898 - [initscripts] Log boot messages to /var/log

Attached to Project: Arch Linux
Opened by Jed Brown (jedbrown) - Tuesday, 22 June 2010, 12:08 GMT
Last edited by Thomas Bächler (brain0) - Tuesday, 22 June 2010, 15:59 GMT
Task Type Feature Request
Category System
Status Closed
Assigned To Aaron Griffin (phrakture)
Thomas Bächler (brain0)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Sometimes error and warning messages are generated late during rc.conf (e.g. while loading daemons). These messages are printed to the console, but these messages are not logged anywhere and (by default) the screen is immediately cleared, essentially preventing the user from reading the messages. As far as I know, the only way to actually read the messages is to disable clearing of the console (http://wiki.archlinux.org/index.php/Disable_Clearing_of_Boot_Messages) and scroll back in tty1 (not an ideal reading environment). The messages currently do not go anywhere in /var/log (though dmesg and other logs may contain indirect evidence of what happened), I propose logging the messages to /var/log/boot.log so that it can be inspected conveniently.
This task depends upon

Closed by  Thomas Bächler (brain0)
Tuesday, 22 June 2010, 15:59 GMT
Reason for closing:  Duplicate
Additional comments about closing:   FS#18046 
Comment by Aaron Griffin (phrakture) - Tuesday, 22 June 2010, 15:50 GMT
It should be fairly easy to redirect the text from the message functions to a file in /var/log. What do you think, Thomas?

The problem with this is that we need to redirect ALL output from ALL apps called from initscripts. Is there a cleaner way to do this with tee? rc.sysinit | tee > /var/log/boot.log ?

Loading...