| To: | linux-kernel@xxxxxxxxxxxxxxx |
|---|---|
| Subject: | Re: patch for common networking error messages |
| From: | Jeff Garzik <jgarzik@xxxxxxxxx> |
| Date: | Mon, 16 Jun 2003 18:52:10 -0400 |
| Cc: | Janice M Girouard <janiceg@xxxxxxxxxx>, "David S. Miller" <davem@xxxxxxxxxx>, netdev@xxxxxxxxxxx, Daniel Stekloff <stekloff@xxxxxxxxxx>, Janice Girouard <girouard@xxxxxxxxxx>, Larry Kessler <lkessler@xxxxxxxxxx>, kenistonj@xxxxxxxxxx |
| In-reply-to: | <3EEE492E.9080308@pobox.com> |
| Organization: | none |
| References: | <3EEE28DE.6040808@us.ibm.com> <20030616.133841.35533284.davem@redhat.com> <3EEE2F9F.60706@us.ibm.com> <3EEE492E.9080308@pobox.com> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
| User-agent: | Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021213 Debian/1.2.1-2.bunk |
Jeff Garzik wrote:
3) _Somebody_ needs to do some "ground pounding", and figure out what info sysadmins and users want to see. Event logging in general, so far, seems to me more like a management checklist item than a real user need... but I am quite willing to be proved wrong. Until we get feedback along these lines, I tend to resist changes like this in general. My initial read of your attached patch was that it was a long of source churn, and I couldn't fathom what any user would gain from it
There are a whole bunch of netif_msg_xxx and corresponding NETIF_MSG_xxx bits. I don't see much need to change that I think getting the logging API right for those would be an important first step.
Jeff |
| Previous by Date: | Re: patch for common networking error messages, Nivedita Singhvi |
|---|---|
| Next by Date: | Re: patch for common networking error messages, David S. Miller |
| Previous by Thread: | Re: patch for common networking error messages, Jeff Garzik |
| Next by Thread: | Re: patch for common networking error messages, Nivedita Singhvi |
| Indexes: | [Date] [Thread] [Top] [All Lists] |