public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Zoltan Menyhart <Zoltan.Menyhart@bull.net>
To: linux-kernel@vger.kernel.org
Subject: Re:  Event logging vs enhancing printk
Date: Wed, 10 Apr 2002 10:21:19 +0200	[thread overview]
Message-ID: <3CB3F5FF.7EBD0A19@bull.net> (raw)
In-Reply-To: <OF7FF94B66.91DD315B-ON88256B95.00811EF0@boulder.ibm.com>

I am definitely *FOR* adding Enterprise Event Logging feature to Linux.

We are going to make "not too small, not too cheap" IA64 based machines
at Bull.
Having a full featured event logging subsystem is essential to provide
good services to our clients.

Most of the HW errors are just impossible to print out to the screen
(and capture them).
There are lots of boring details, binary data, it's not a print that
will help us.

People are negligent with prints. They feel free to print out anything
they think it is important.
You'll need an artificial intelligence if you want to make status
reports out of random prints.

Not losing error logs is essential.
I need a feed-back from the error logging subsystem saying that the log
is already stored on a permanent storage before I clear the firmware's
error report.

We should do at leas as well as Windows does the error handling, or even
better :-)

I am convenienced that Linux becomes a professional system and it needs
professional tools.

Thanks,

Zoltan Menyhart

P.S.: Please CC your answers to Zoltan.Menyhart@bull.net

       reply	other threads:[~2002-04-10  8:21 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <OF7FF94B66.91DD315B-ON88256B95.00811EF0@boulder.ibm.com>
2002-04-10  8:21 ` Zoltan Menyhart [this message]
     [not found] <Pine.LNX.4.33.0204111358000.20722-100000@coffee.psychology.mcmaster.ca>
2002-04-12  9:30 ` Event logging vs enhancing printk Zoltan Menyhart
2002-04-12 12:41   ` Mark Hahn
2002-04-12 14:38     ` Martin J. Bligh
2002-04-12 18:04       ` Karim Yaghmour
2002-04-10 19:43 Larry Kessler
  -- strict thread matches above, loose matches on Subject: below --
2002-04-10 17:13 Francois-Xavier Kowalski
2002-04-10 15:55 Larry Kessler
     [not found] <OF58E93BB4.1862769F-ON85256B97.0047811A@pok.ibm.com>
2002-04-10 14:19 ` sullivan
2002-04-10 13:08 Michael Holzheu
2002-04-08 23:18 Martin J. Bligh
2002-04-08 22:38 ` Andrew Morton
2002-04-08 23:54   ` Martin J. Bligh
2002-04-08 23:07     ` Andrew Morton
2002-04-09  2:14       ` Martin J. Bligh
2002-04-10  1:23         ` Andrea Arcangeli
2002-04-10  5:28           ` Martin J. Bligh
2002-04-11  0:15             ` Andrea Arcangeli
2002-04-09 14:34     ` Bill Davidsen
2002-04-09 14:50       ` Martin J. Bligh
2002-04-09 13:24 ` Denis Vlasenko
2002-04-09 14:42   ` Martin J. Bligh
2002-04-09 18:17     ` John Alvord
2002-04-09 14:21 ` Michel Dagenais
2002-04-09 20:49   ` Brian Beattie
2002-04-09 21:16     ` Martin J. Bligh
2002-04-09 22:28       ` Brian Beattie
2002-04-10  0:29         ` Brian Beattie
2002-04-10  1:17         ` Martin J. Bligh
2002-04-10 11:24     ` Denis Vlasenko
2002-04-11 15:11     ` Michel Dagenais

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3CB3F5FF.7EBD0A19@bull.net \
    --to=zoltan.menyhart@bull.net \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox