From owner-freebsd-stable Tue Sep 3 3:22:26 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E116237B400 for ; Tue, 3 Sep 2002 03:22:23 -0700 (PDT) Received: from south.nanolink.com (south.nanolink.com [217.75.134.10]) by mx1.FreeBSD.org (Postfix) with SMTP id 4CC6143E4A for ; Tue, 3 Sep 2002 03:22:22 -0700 (PDT) (envelope-from roam@ringlet.net) Received: (qmail 5929 invoked by uid 85); 3 Sep 2002 10:30:52 -0000 Received: from office.sbnd.net (HELO straylight.ringlet.net) (217.75.131.130) by south.nanolink.com with SMTP; 3 Sep 2002 10:30:51 -0000 Received: (qmail 40302 invoked by uid 1000); 3 Sep 2002 10:21:19 -0000 Date: Tue, 3 Sep 2002 13:21:19 +0300 From: Peter Pentchev To: Paolo Cc: freebsd-stable@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: to log the output of rc scripts Message-ID: <20020903102119.GC39422@straylight.oblivion.bg> Mail-Followup-To: Paolo , freebsd-stable@freebsd.org, freebsd-hackers@freebsd.org References: <20020902183524.A69527@linux.netline.it> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="z4+8/lEcDcG5Ke9S" Content-Disposition: inline In-Reply-To: <20020902183524.A69527@linux.netline.it> User-Agent: Mutt/1.5.1i X-Virus-Scanned: by Nik's Monitoring Daemon (AMaViS perl-11d ) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --z4+8/lEcDcG5Ke9S Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Sep 02, 2002 at 06:35:24PM +0200, Paolo wrote: > Hi all! > I need to administer remotely a bunch of freebsd boxes. I would > be very useful to have access to the output of the rc scripts to see, for > example, if a cvsup session has worked correctly... > Is it there an option to force logging the output of the rc scripts? > Would it be useful if I started working on the subject? I believe that, in general, 'dmesg -a' should do what you want. A quick and easy solution, off the top of my head, would be to add an /usr/local/etc/rc.d/ZZZZZZZZ.savemessages.sh script, which does something like dmesg -a > /var/log/dmesg-afterboot.log or the like. G'luck, Peter --=20 Peter Pentchev roam@ringlet.net roam@FreeBSD.org PGP key: http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint FDBA FD79 C26F 3C51 C95E DF9E ED18 B68D 1619 4553 This sentence contains exactly threee erors. --z4+8/lEcDcG5Ke9S Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (FreeBSD) iD8DBQE9dI0f7Ri2jRYZRVMRAv8XAKCDOJ+UHUjiKWZLIp23JxAvqTrmpgCfVg/Y Gv+NwueFas4oWSuUnl7n4Bc= =WBX/ -----END PGP SIGNATURE----- --z4+8/lEcDcG5Ke9S-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message