From owner-freebsd-embedded@FreeBSD.ORG Sat Feb 13 02:32:44 2010 Return-Path: Delivered-To: embedded@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4B444106566C for ; Sat, 13 Feb 2010 02:32:44 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id 0E3AE8FC08 for ; Sat, 13 Feb 2010 02:32:43 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.14.3/8.14.1) with ESMTP id o1D2SusD051473; Fri, 12 Feb 2010 19:28:56 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Fri, 12 Feb 2010 19:29:03 -0700 (MST) Message-Id: <20100212.192903.756786594423214367.imp@bsdimp.com> To: mah@jump-ing.de From: "M. Warner Losh" In-Reply-To: References: <61B7DB7D-CFF0-4691-9693-E289A685A183@jump-ing.de> <20100212203912.GA79178@psconsult.nl> X-Mailer: Mew version 6.3 on Emacs 22.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: embedded@FreeBSD.org Subject: Re: Catching /etc/rc's output X-BeenThere: freebsd-embedded@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Dedicated and Embedded Systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Feb 2010 02:32:44 -0000 In message: Markus Hitter 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