Date: 12 Sep 1999 21:10:39 +0200 From: Dag-Erling Smorgrav <des@flood.ping.uio.no> To: "Rodney W. Grimes" <freebsd@gndrsh.dnsmgr.net> Cc: hackers@freebsd.org Subject: Re: How to prevent motd including os info Message-ID: <xzp671g0wuo.fsf@flood.ping.uio.no> In-Reply-To: "Rodney W. Grimes"'s message of "Sun, 12 Sep 1999 12:04:22 -0700 (PDT)" References: <199909121904.MAA31397@gndrsh.dnsmgr.net>
next in thread | previous in thread | raw e-mail | index | archive | help
"Rodney W. Grimes" <freebsd@gndrsh.dnsmgr.net> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?xzp671g0wuo.fsf>