From owner-freebsd-hackers Wed Jul 24 09:30:15 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA27898 for hackers-outgoing; Wed, 24 Jul 1996 09:30:15 -0700 (PDT) Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.109.160]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA27890 for ; Wed, 24 Jul 1996 09:30:12 -0700 (PDT) Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id LAA14277; Wed, 24 Jul 1996 11:29:04 -0500 From: Joe Greco Message-Id: <199607241629.LAA14277@brasil.moneng.mei.com> Subject: Re: catching /etc/rc output To: hans@brandinnovators.com (Hans Zuidam) Date: Wed, 24 Jul 1996 11:29:04 -0500 (CDT) Cc: freebsd-hackers@freebsd.org In-Reply-To: <199607241503.RAA01095@truk.brandinnovators.com> from "Hans Zuidam" at Jul 24, 96 05:03:53 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Hi, > > Is there a convenient way to direct all output from the /etc/rc scripts > to both the console and a file other than rewriting them? Scrollback > is not always sufficient especially after lengthy fsck output. Not that I'm aware of :-) At one point I had rewritten some of SunOS's startup scripts to redirect all output to a file, this was sorta useful. One could conceivably "tail -f" the file to the console to obtain functionality similar to what you ask for. The lazy among us might choose to use serial consoles instead, as it would allow another machine running kermit with a log file to maintain long term console records. The very lazy among us (i.e. me) might even plan to use a session manager such as screen to handle multiple consoles simultaneously, and also this provides remote console access. However the very lazy among us will have been talking about it rather than doing it for the last year or so. :-) There's always a more important fire burning.. ... JG