From owner-freebsd-hackers Sun Sep 12 12:10:46 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 41DA214DBB for ; Sun, 12 Sep 1999 12:10:43 -0700 (PDT) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id VAA15244; Sun, 12 Sep 1999 21:10:39 +0200 (CEST) (envelope-from des) To: "Rodney W. Grimes" Cc: hackers@freebsd.org Subject: Re: How to prevent motd including os info References: <199909121904.MAA31397@gndrsh.dnsmgr.net> From: Dag-Erling Smorgrav Date: 12 Sep 1999 21:10:39 +0200 In-Reply-To: "Rodney W. Grimes"'s message of "Sun, 12 Sep 1999 12:04:22 -0700 (PDT)" Message-ID: Lines: 22 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Rodney W. Grimes" writes: > > One thing I'd like very much, though, would be to have the output of > > fsck -p logged somehow [...] > Actually I would like _all_ the output from /etc/rc* to be avaliable > after boot. It should be in the syscons scroll back buffer, [...] No. The scrollback may be too short (especially after an fsck of a large filesystem after a crash), and it may even be empty (if you put something like VESA_132x60 in allscreens_flags in rc.conf) > And solving only 1 piece of output from /etc/rc is an incomplete > concept. I really like to know if ntpdate stepped my clock 230000 seconds > for some reason, thats why this (usually means a clock chip has gone > zonkers :-)): Doesn't ntpdate log what it does with syslog? If not, I think whichever syscall it is that ntpdate uses to adjust the time should printf() or log() the change. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message