From owner-freebsd-arch Tue Aug 20 4:32:34 2002 Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A265837B400 for ; Tue, 20 Aug 2002 04:32:31 -0700 (PDT) Received: from mailout03.sul.t-online.com (mailout03.sul.t-online.com [194.25.134.81]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1BFD643E65 for ; Tue, 20 Aug 2002 04:32:30 -0700 (PDT) (envelope-from Alexander@Leidinger.net) Received: from fwd01.sul.t-online.de by mailout03.sul.t-online.com with smtp id 17h7FM-0005ON-0M; Tue, 20 Aug 2002 13:32:28 +0200 Received: from Andro-Beta.Leidinger.net (520065502893-0001@[217.229.217.127]) by fmrl01.sul.t-online.com with esmtp id 17h7FD-1OJhpoC; Tue, 20 Aug 2002 13:32:19 +0200 Received: from Magelan.Leidinger.net (Magelan [192.168.1.1]) by Andro-Beta.Leidinger.net (8.11.6/8.11.6) with ESMTP id g7KBWGx88900 for ; Tue, 20 Aug 2002 13:32:16 +0200 (CEST) (envelope-from Alexander@Leidinger.net) Received: from Magelan.Leidinger.net (netchild@localhost [127.0.0.1]) by Magelan.Leidinger.net (8.12.5/8.12.5) with SMTP id g7KBWFc1009455 for ; Tue, 20 Aug 2002 13:32:15 +0200 (CEST) (envelope-from Alexander@Leidinger.net) Date: Tue, 20 Aug 2002 13:32:15 +0200 From: Alexander Leidinger To: arch@freebsd.org Subject: timestamping kernel messages Message-Id: <20020820133215.0545063d.Alexander@Leidinger.net> Organization: Independend X-Mailer: Sylpheed version 0.8.1claws (GTK+ 1.2.10; i386-portbld-freebsd5.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Sender: 520065502893-0001@t-dialin.net Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG 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 know, this breaks syslogs ability to group messages ("last message repeated X times") and the timestamp already exits in e.g. /var/log/messages, but I think it may be useful in some scenarios (e.g. only remote syslog available but you have to hurry, or emergency failure diagnostics with a reboot slave on the phone while you are sitting in the bath tub) to at least make it a kernel option. Is there enough support for this feature to get it into the tree, and if yes, where should I start to look to implement this feature? I don't mind if someone else is interested enough to do it on their own, I have enough on my TODO list already, but feel free to contact me for my feature requests if you want to do the work. Bye, Alexander. -- "One world, one web, one program" -- Microsoft promotional ad "Ein Volk, ein Reich, ein Fuehrer" -- Adolf Hitler http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message