Date: Mon, 18 Dec 2000 07:35:24 +0100 From: Poul-Henning Kamp <phk@critter.freebsd.dk> To: John Baldwin <jhb@FreeBSD.ORG> Cc: Doug Barton <DougB@gorean.org>, current@FreeBSD.ORG Subject: Re: test/review: /dev/console logging patch Message-ID: <25628.977121324@critter> In-Reply-To: Your message of "Sun, 17 Dec 2000 15:06:40 PST." <XFMail.001217150640.jhb@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
>>> >>> This patch is for the printf(9), log(9) & /dev/console stuff. >>> The result is that you can watch the output from /etc/rc in >>> your /var/log/messages. >> >> Dec 17 13:00:26 <console.info> Master /boot/kernel/kernel: Doing >> additional network setup: >> Dec 17 13:00:26 <console.info> Master /boot/kernel/kernel: ntpdate >> Dec 17 13:00:26 <console.info> Master /boot/kernel/kernel: ntpd >> Dec 17 13:00:27 <console.info> Master /boot/kernel/kernel: portmap >> Dec 17 13:00:27 <console.info> Master /boot/kernel/kernel: . > >The '.'s are simple and not too cluttery. Fixing the console to line buffer >what it sends to log(9) is a better fix, IMO. I specifically decided not to do this because I want to be able to see stuff like: echo -n "Press return to avoid disaster: " > /dev/console read < /dev/console Of course one could add timeouts and what's not, but then imagine the case of two programs writing on /dev/console at the same time... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?25628.977121324>