Linux - General This Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place. |
| Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
 |
GNU/Linux Basic Guide
This 255-page guide will provide you with the keys to understand the philosophy of free software, teach you how to use and handle it, and give you the tools required to move easily in the world of GNU/Linux. Many users and administrators will be taking their first steps with this GNU/Linux Basic guide and it will show you how to approach and solve the problems you encounter.
Click Here to receive this Complete Guide absolutely free. |
|
 |
06-19-2005, 01:06 PM
|
#1
|
|
Member
Registered: Jul 2003
Posts: 46
Rep:
|
Logging Console Boot Messages
Hi, I am getting some output during boot up that does not appear in any of the log files in /var/log. How can I get access to these messages? I would like them logged in the future...that is, I would like to have a log file that is an exact duplicate of the output I see during bootup (no extra details, no missing details...just an exact duplicate).
|
|
|
|
06-19-2005, 02:02 PM
|
#2
|
|
Senior Member
Registered: Jul 2004
Location: Denmark
Distribution: Ubuntu, Debian
Posts: 1,524
Rep:
|
The naive brute-force solution would be to use tee (man tee) to, well, tee stdout to /where/ever/stdout.log; similarly for stderr.
I do believe (hope, at least), however, that better solutions exist. I wouldn't know any
hth --Jonas
|
|
|
|
06-19-2005, 02:12 PM
|
#3
|
|
Member
Registered: Feb 2003
Location: Richmond VA
Distribution: Slackware 11 -- CentOS 4.4
Posts: 115
Rep:
|
Did you look in /etc/syslog.conf ?
look for a line that has /dev/console on the right side like
kern.warning /dev/console
("kern.warning" is just an example)
change /dev/console to /var/log/<mybootmessages>
and you need to run from the command line:
touch /var/log/<mybootmessages>
(of course naming this latter file whatever )
HTH
|
|
|
|
06-19-2005, 02:24 PM
|
#4
|
|
Member
Registered: Jul 2003
Posts: 46
Original Poster
Rep:
|
If I change the output from /dev/console to a log file, then I won't see it at the console anymore. I could try tee, but there should be a nice way to keep the output going to console...additionally, it should log these to a file. Note, to see the display before I log in, I could hold down shift and press page-up. This will allow me to see the messages...so this is stored in some buffer. Can't I output the buffer to a file?
|
|
|
|
06-19-2005, 02:38 PM
|
#6
|
|
Member
Registered: Feb 2003
Location: Richmond VA
Distribution: Slackware 11 -- CentOS 4.4
Posts: 115
Rep:
|
after boot is completed,
as root;
dmesg |more
of course this isn't everything that scrolled by on boot ...
|
|
|
|
| Thread Tools |
Search this Thread |
|
|
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -5. The time now is 04:34 PM.
|
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|