Date: Fri, 12 Feb 2010 19:29:03 -0700 (MST) From: "M. Warner Losh" <imp@bsdimp.com> To: mah@jump-ing.de Cc: embedded@FreeBSD.org Subject: Re: Catching /etc/rc's output Message-ID: <20100212.192903.756786594423214367.imp@bsdimp.com> In-Reply-To: <CD175D72-0E1A-4F8D-870B-E9509EAEE51A@jump-ing.de> References: <61B7DB7D-CFF0-4691-9693-E289A685A183@jump-ing.de> <20100212203912.GA79178@psconsult.nl> <CD175D72-0E1A-4F8D-870B-E9509EAEE51A@jump-ing.de>
index | next in thread | previous in thread | raw e-mail
In message: <CD175D72-0E1A-4F8D-870B-E9509EAEE51A@jump-ing.de>
Markus Hitter <mah@jump-ing.de> writes:
:
: Am 12.02.2010 um 21:39 schrieb Paul Schenkeveld:
:
: > On Fri, Feb 12, 2010 at 05:52:44PM +0100, Markus Hitter wrote:
: >>
: >> Hello all,
: >>
: >> it's seemingly such a basic question, but I can't find a way to
: >> redirect
: >> /etc/rc's output to a file. Editing /etc/syslog.conf changed nothing,
: >> /var/log/messages still stops where /etc/rc should begin. I can see
: >> the
: >> output on the console, but that's far to fast for the human eye. Short
: >> of
: >> hooking up a serial console to catch the log on a second machine, is
: >> there
: >> a way to get this output logged into a file?
: >
: > Try 'dmesg -a'
:
: That's it. Thanks, Paul.
:
: Obviously, this stuff is in RAM only, so searching the file system was
: the wrong place ...
Well, you can also put the following in your syslog.conf:
console.info /var/log/console.log
and reboot or restart things in the usual way. Maybe that's what you
are looking for?
Warner
help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100212.192903.756786594423214367.imp>