Date: Tue, 20 Aug 2002 13:35:22 +0200 From: Poul-Henning Kamp <phk@critter.freebsd.dk> To: Alexander Leidinger <Alexander@Leidinger.net> Cc: arch@FreeBSD.ORG Subject: Re: timestamping kernel messages Message-ID: <24056.1029843322@critter.freebsd.dk> In-Reply-To: Your message of "Tue, 20 Aug 2002 13:32:15 %2B0200." <20020820133215.0545063d.Alexander@Leidinger.net>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <20020820133215.0545063d.Alexander@Leidinger.net>, Alexander Leidinger wr ites: >Hi, > >what do you think about using timestamps in kernel messages? > >Long: >I think it would be useful to have timestamps in kernel warnings, e.g. >(sa0:ahc0:0:1:0): tape is now frozen- use an OFFLINE, REWIND or MTEOM command to clear this state >should be prefixed by a timestamp to be able to determine the importance >of messages / make it easier to correlate this messages with other >events just by looking at the console. I think we need to revamp the console/logging system in toto. I think we should have a pseudo-device for console/log use, which stores thing in a circular buffer. Syslogd would then retreive stuff from that buffer, somewhat like what it does today. For tty console usage, we should have a kernel thread which picks things out of the buffer and prints it on the chosen console, and putting a timestamp on it would be a Good Thing. This would also give us a good architecture for hooking up ethernet consoles. -- 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-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?24056.1029843322>