From owner-freebsd-hackers Sun Sep 12 15:30:48 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id 94E4E14D84 for ; Sun, 12 Sep 1999 15:30:44 -0700 (PDT) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id PAA31675; Sun, 12 Sep 1999 15:30:39 -0700 (PDT) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <199909122230.PAA31675@gndrsh.dnsmgr.net> Subject: Re: How to prevent motd including os info In-Reply-To: from Dag-Erling Smorgrav at "Sep 12, 1999 09:10:39 pm" To: des@flood.ping.uio.no (Dag-Erling Smorgrav) Date: Sun, 12 Sep 1999 15:30:38 -0700 (PDT) Cc: hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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) We can tune the size of the scroll back buffer can't we? And fsck output even after a crash is usually not that long, if it gets long it usually has more problems than fsck -p can deal with and stops any way. Why does switching display mode screw up the scroll back buffer? That sounds broken to me. > > > 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. If you give it the -s option, yes it will syslog it. But doing that to everything in /etc/rc* seems like a pain in the *ss... -- Rod Grimes - KD7CAX - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message