Date: Wed, 19 Feb 2003 22:37:59 +0000 From: Scott Mitchell <scott+freebsd@fishballoon.org> To: Wayne Lubin <wayneclubin@yahoo.com> Cc: Scott Mitchell <scott@fishballoon.org>, freebsd-questions@FreeBSD.ORG Subject: Re: Where can i find a startup log Message-ID: <20030219223759.GB409@tuatara.fishballoon.org> In-Reply-To: <20030219193405.48195.qmail@web41304.mail.yahoo.com> References: <20030219182456.GA66250@tuatara.fishballoon.org> <20030219193405.48195.qmail@web41304.mail.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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 majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030219223759.GB409>