Where can i find a startup log
Hi list, I hope this isn't a FAQ - i have been using FreeBSD for some years now. My question: Where can i find a log of all the startup messages that flash by so fast that i can't read them? Not the kernel messages, but daemons that fail to start and such. I have been searching the web, handbook, faq, but to no avail. Thanks for any hints Heinrich -- Heinrich Rebehn University of Bremen Physics / Electrical and Electronics Engineering - Department of Telecommunications - E-mail: mailto:[EMAIL PROTECTED] Phone : +49/421/218-4664 Fax :-3341 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Where can i find a startup log
At 15:53 19.02.2003 +0100, you wrote: Hi list, I hope this isn't a FAQ - i have been using FreeBSD for some years now. My question: Where can i find a log of all the startup messages that flash by so fast that i can't read them? Not the kernel messages, but daemons that fail to start and such. Type: dmesg or do a # more /var/log/messages /Andreas --- Andreas Widerøe Andersen [EMAIL PROTECTED] Pragma AS http://www.pragma.no To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Where can i find a startup log
Andreas Widerøe Andersen wrote: At 15:53 19.02.2003 +0100, you wrote: Hi list, I hope this isn't a FAQ - i have been using FreeBSD for some years now. My question: Where can i find a log of all the startup messages that flash by so fast that i can't read them? Not the kernel messages, but daemons that fail to start and such. Type: dmesg or do a # more /var/log/messages /Andreas This only gives me the kernel messages, but not the messages from the daemons (i.e. sendmail failed and stuff like that) Heinrich To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Where can i find a startup log
On Wed, Feb 19, 2003 at 04:12:56PM +0100, Heinrich Rebehn wrote: Andreas Widerøe Andersen wrote: At 15:53 19.02.2003 +0100, you wrote: I hope this isn't a FAQ - i have been using FreeBSD for some years now. My question: Where can i find a log of all the startup messages that flash by so fast that i can't read them? Not the kernel messages, but daemons that fail to start and such. Type: dmesg or do a # more /var/log/messages This only gives me the kernel messages, but not the messages from the daemons (i.e. sendmail failed and stuff like that) Edit /etc/syslog.conf and uncomment the console.info line so that is looks like this: # uncomment this to log all writes to /dev/console to /var/log/console.log console.info/var/log/console.log Then: # touch /var/log/console.log # chmod 600 /var/log/console.log # chown root:wheel /var/log/console/log # kill -HUP `cat /var/run/syslogd.pid` This will record all of the console output from syslog or the kernel, as well as the boot messages you are interested in, the next time you reboot. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way PGP: http://www.infracaninophile.co.uk/pgpkey Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Where can i find a startup log
Matthew Seaman wrote: On Wed, Feb 19, 2003 at 04:12:56PM +0100, Heinrich Rebehn wrote: Andreas Widerøe Andersen wrote: At 15:53 19.02.2003 +0100, you wrote: I hope this isn't a FAQ - i have been using FreeBSD for some years now. My question: Where can i find a log of all the startup messages that flash by so fast that i can't read them? Not the kernel messages, but daemons that fail to start and such. Type: dmesg or do a # more /var/log/messages This only gives me the kernel messages, but not the messages from the daemons (i.e. sendmail failed and stuff like that) Edit /etc/syslog.conf and uncomment the console.info line so that is looks like this: # uncomment this to log all writes to /dev/console to /var/log/console.log console.info/var/log/console.log Then: # touch /var/log/console.log # chmod 600 /var/log/console.log # chown root:wheel /var/log/console/log # kill -HUP `cat /var/run/syslogd.pid` This will record all of the console output from syslog or the kernel, as well as the boot messages you are interested in, the next time you reboot. Cheers, Matthew Thanks, Matthew this really did the trick. One is never finished learning.. :-) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Where can i find a startup log
--- Matthew Seaman [EMAIL PROTECTED] wrote: On Wed, Feb 19, 2003 at 04:12:56PM +0100, Heinrich Rebehn wrote: Andreas Widerøe Andersen wrote: At 15:53 19.02.2003 +0100, you wrote: I hope this isn't a FAQ - i have been using FreeBSD for some years now. My question: Where can i find a log of all the startup messages that flash by so fast that i can't read them? Not the kernel messages, but daemons that fail to start and such. Type: dmesg or do a # more /var/log/messages This only gives me the kernel messages, but not the messages from the daemons (i.e. sendmail failed and stuff like that) Edit /etc/syslog.conf and uncomment the console.info line so that is looks like this: # uncomment this to log all writes to /dev/console to /var/log/console.log console.info /var/log/console.log Then: # touch /var/log/console.log # chmod 600 /var/log/console.log # chown root:wheel /var/log/console/log # kill -HUP `cat /var/run/syslogd.pid` This will record all of the console output from syslog or the kernel, as well as the boot messages you are interested in, the next time you reboot. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way PGP: http://www.infracaninophile.co.uk/pgpkey Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message I don't understand what exactly is being suggested here. The part I don't understand is what is being said to done with Then: # touch /var/log/console.log # chmod 600 /var/log/console.log # chown root:wheel /var/log/console/log # kill -HUP `cat /var/run/syslogd.pid` Are you suggesting that we add those comments to the file, which obviously does not make sense. Or are you suggesting that we uncomment those lines, but in which case does not make sense because those lines don't exist in my file. Or are you suggesting that we add those lines in uncommented form to the file. Below is a copy of my syslog.conf file # $FreeBSD: src/etc/syslog.conf,v 1.13.2.3 2002/04/15 00:44:13 dougb Exp $ # # Spaces ARE valid field separators in this file. However, # other *nix-like systems still insist on using tabs as field # separators. If you are sharing this file between systems, you # may want to use only tabs as field separators here. # Consult the syslog.conf(5) manpage. *.err;kern.debug;auth.notice;mail.crit /dev/console *.notice;kern.debug;lpr.info;mail.crit;news.err /var/log/messages security.* /var/log/security auth.info;authpriv.info /var/log/auth.log mail.info /var/log/maillog lpr.info /var/log/lpd-errs cron.* /var/log/cron *.emerg * # uncomment this to log all writes to /dev/console to /var/log/console.log #console.info /var/log/console.log # uncomment this to enable logging of all log messages to /var/log/all.log # touch /var/log/all.log and chmod it to mode 600 before it will work #*.* /var/log/all.log # uncomment this to enable logging to a remote loghost named loghost #*.* @loghost # uncomment these if you're running inn # news.crit /var/log/news/news.crit # news.err /var/log/news/news.err # news.notice /var/log/news/news.notice !startslip *.* /var/log/slip.log !ppp *.* /var/log/ppp.log Thanks __ Do you Yahoo!? Yahoo! Shopping - Send Flowers for Valentine's Day http://shopping.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Where can i find a startup log
On Wed, 19 Feb 2003 at 09:50:16 -0800, Wayne Lubin wrote: --snip-- I don't understand what exactly is being suggested here. The part I don't understand is what is being said to done with Then: # touch /var/log/console.log # chmod 600 /var/log/console.log # chown root:wheel /var/log/console/log # kill -HUP `cat /var/run/syslogd.pid` Are you suggesting that we add those comments to the file, which obviously does not make sense. Or are you suggesting that we uncomment those lines, but in which case does not make sense because those lines don't exist in my file. Or are you suggesting that we add those lines in uncommented form to the file. --snip-- Thanks Actually what he meant (wrote) is that you uncomment the line in syslogd.conf, then from the command line run the touch, chmod, chown, and kill. the #'s in 4 lines happen to be shell prompts -Andrew -- Andrew Stuart http://www.tekrealm.net President Thieu says he'll quit if he doesn't get more than 50% of the vote. In a democracy, that's not called quitting. -- The Washington Post msg19896/pgp0.pgp Description: PGP signature
Re: Where can i find a startup log
On Wed, Feb 19, 2003 at 09:50:16AM -0800, Wayne Lubin wrote: I don't understand what exactly is being suggested here. The part I don't understand is what is being said to done with Then: # touch /var/log/console.log # chmod 600 /var/log/console.log # chown root:wheel /var/log/console/log # kill -HUP `cat /var/run/syslogd.pid` Are you suggesting that we add those comments to the file, which obviously does not make sense. Or are you suggesting that we uncomment those lines, but in which case does not make sense because those lines don't exist in my file. Or are you suggesting that we add those lines in uncommented form to the file. He's suggesting you run those commands in your shell after making the edits to syslog.conf. The '#' means you need to run the commands as root (it's a typical shell prompt for root logins). HTH, Scott To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Where can i find a startup log
--- Scott Mitchell [EMAIL PROTECTED] wrote: On Wed, Feb 19, 2003 at 09:50:16AM -0800, Wayne Lubin wrote: I don't understand what exactly is being suggested here. The part I don't understand is what is being said to done with Then: # touch /var/log/console.log # chmod 600 /var/log/console.log # chown root:wheel /var/log/console/log # kill -HUP `cat /var/run/syslogd.pid` Are you suggesting that we add those comments to the file, which obviously does not make sense. Or are you suggesting that we uncomment those lines, but in which case does not make sense because those lines don't exist in my file. Or are you suggesting that we add those lines in uncommented form to the file. He's suggesting you run those commands in your shell after making the edits to syslog.conf. The '#' means you need to run the commands as root (it's a typical shell prompt for root logins). HTH, Scott To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message Ahh ok. What confused me was that there were similar looking statements already contained in the syslog.conf file. With that in mind I now see the purpose of all of the commands except the last one. For what reason does one have to perform kill -HUP `cat /var/run/syslogd.pid` In other words why must one stop the syslogd daemon? It will only start up again upon the next reboot. And one more question. after doing the above things, to see the the full listing of boot up messages does one still only need to do a dmesg? Thanks again. __ Do you Yahoo!? Yahoo! Shopping - Send Flowers for Valentine's Day http://shopping.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Where can i find a startup log
On Wed, Feb 19, 2003 at 11:34:05AM -0800, Wayne Lubin wrote: [...] With that in mind I now see the purpose of all of the commands except the last one. For what reason does one have to perform kill -HUP `cat /var/run/syslogd.pid` In other words why must one stop the syslogd daemon? It will only start up again upon the next reboot. This doesn't stop the syslogd daemon. It's a notification signal to syslogd to re-read the /etc/syslog.conf. Check out syslogd(8) for more details. -- Jonathan Chen [EMAIL PROTECTED] -- If you wish your merit to be known, acknowledge that of other people To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Where can i find a startup log
On Wed, Feb 19, 2003 at 11:34:05AM -0800, Wayne Lubin wrote: Ahh ok. What confused me was that there were similar looking statements already contained in the syslog.conf file. With that in mind I now see the purpose of all of the commands except the last one. For what reason does one have to perform kill -HUP `cat /var/run/syslogd.pid` In other words why must one stop the syslogd daemon? It will only start up again upon the next reboot. And one more question. after doing the above things, to see the the full listing of boot up messages does one still only need to do a dmesg? Hi Wayne, I think Jonathan answered the first part of your question... as for the second part, you'll need to look in /var/log/console.log as well as the dmesg output. Cheers, Scott To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Where can i find a startup log
'dmesg' /var/log/messages On Wed, 19 Feb 2003 15:53:43 +0100 Heinrich Rebehn [EMAIL PROTECTED] wrote: Hi list, I hope this isn't a FAQ - i have been using FreeBSD for some years now. My question: Where can i find a log of all the startup messages that flash by so fast that i can't read them? Not the kernel messages, but daemons that fail to start and such. I have been searching the web, handbook, faq, but to no avail. Thanks for any hints Heinrich -- Heinrich Rebehn University of Bremen Physics / Electrical and Electronics Engineering - Department of Telecommunications - E-mail: mailto:[EMAIL PROTECTED] Phone : +49/421/218-4664 Fax :-3341 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message -- Bore, n.: A person who talks when you wish him to listen. -- Ambrose Bierce, The Devil's Dictionary ---FreeBSD The Power To Serve--- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
