From owner-freebsd-embedded@FreeBSD.ORG Fri Feb 12 20:59:28 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 464EB1065672 for ; Fri, 12 Feb 2010 20:59:28 +0000 (UTC) (envelope-from fb-embedded@psconsult.nl) Received: from mx1.psconsult.nl (psc11.adsl.iaf.nl [80.89.238.138]) by mx1.freebsd.org (Postfix) with ESMTP id CFFD28FC0C for ; Fri, 12 Feb 2010 20:59:27 +0000 (UTC) Received: from mx1.psconsult.nl (localhost [80.89.238.138]) by mx1.psconsult.nl (8.14.2/8.14.2) with ESMTP id o1CKdDrq079213 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 12 Feb 2010 21:39:18 +0100 (CET) (envelope-from fb-embedded@psconsult.nl) Received: (from paul@localhost) by mx1.psconsult.nl (8.14.2/8.14.2/Submit) id o1CKdCcf079212; Fri, 12 Feb 2010 21:39:12 +0100 (CET) (envelope-from fb-embedded@psconsult.nl) Date: Fri, 12 Feb 2010 21:39:12 +0100 From: Paul Schenkeveld To: freebsd-embedded@freebsd.org, embedded@freebsd.org Message-ID: <20100212203912.GA79178@psconsult.nl> Mail-Followup-To: freebsd-embedded@freebsd.org, embedded@freebsd.org References: <61B7DB7D-CFF0-4691-9693-E289A685A183@jump-ing.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <61B7DB7D-CFF0-4691-9693-E289A685A183@jump-ing.de> User-Agent: Mutt/1.5.17 (2007-11-01) Cc: 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: Fri, 12 Feb 2010 20:59:28 -0000 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' > Thanks, > Markus Paul Schenkeveld