SlackwareThis Forum is for the discussion of Slackware Linux.
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.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I know I can use dmesg to view the output of the kernel system log.
But once the kernel has booted, and init is called to read
/etc/inittab, all the output of the initialization scripts
(eg, /etc/rc.d/rc.S, /etc/rc.d/rc.M, etc) scrolls by so fast
that I can't follow all of it. I'd like to be able to review
it after the system boots. As for as I can tell, all the output
of those initialization scripts is "lost".
Is there some way to save or retrieve the output of the
initialization shell scripts so I can look at it after
the system has booted?
I'm looking for all of the standard output and standard error
from the init scripts. For example,
the first echo statement in /etc/rc.d/rc.M is "Going multiuser...".
dmesg does not capture the echo statements (or more importantly,
and stderr) from the init scripts. They scroll off the screen so
quickly that you can't read or retrieve them. I'd like to be able
to save them all somehow.
No, I had never tried that, and it does allow me to see all the messages.
Thanks! However, I still would really like to save them all to a file
somehow. I still don't know how to do that, but this is certainly better
than never seeing them at all... If anyone knows how to save them to a
file I'd appreciate it if you could tell me how...
dmesg output, /var/log/messages, and /var/log/syslog do not contain the
stderr/stdout of the initialization scripts. That is why I started
this thread. For example, as stated above, /etc/rc.d/rc.M echoes out the
string "Going Multiuser...". dmesg, /var/log/messages,and /var/log/syslog
do not show that string. I'd like to capture it to a file. I'm really looking
to capture the stderr, but stdin would be nice to.
I have noticed that my dmesg, messages and syslog do not contain init script output either.. is it a config option some where to log this stuff? There has got to be a way to dump the <SHIFT> <PAGEUP> buffer to a file.. I'd like to know too.