| To: | Valdis.Kletnieks@xxxxxx |
|---|---|
| Subject: | Re: patch for common networking error messages |
| From: | Stephen Hemminger <shemminger@xxxxxxxx> |
| Date: | Tue, 17 Jun 2003 09:08:59 -0700 |
| Cc: | girouard@xxxxxxxxxx, davem@xxxxxxxxxx, stekloff@xxxxxxxxxx, janiceg@xxxxxxxxxx, jgarzik@xxxxxxxxx, lkessler@xxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, netdev@xxxxxxxxxxx, niv@xxxxxxxxxx |
| In-reply-to: | <200306170434.h5H4YZPZ003025@turing-police.cc.vt.edu> |
| Organization: | Open Source Development Lab |
| References: | <OFCA1A4F38.D782F1D3-ON85256D48.000A5CED@us.ibm.com> <200306170434.h5H4YZPZ003025@turing-police.cc.vt.edu> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
Binary interface's will never cut it. Read the hotplug thread to see how Linus
said, he will never add a binary event daemon interface.
That said, there is an oppurtunity for to provide a ascii interface (similar to
/sbin/hotplug) decodes the data from the rtnetlink interface in a standardized
format.
Then it would be easy to write things like perl monitoring scripts that do
things
like:
perl phone-me-if-network-dies.pl < /proc/net/events
Don't flame me about the choce of name. /proc/net/events is not the right name
to use for such an interface since adding more to /proc is probably not desired.
|
| Previous by Date: | Re: Route cache performance tests, David S. Miller |
|---|---|
| Next by Date: | Re: patch for common networking error messages, David S. Miller |
| Previous by Thread: | Re: patch for common networking error messages, Valdis . Kletnieks |
| Next by Thread: | Re: patch for common networking error messages, David S. Miller |
| Indexes: | [Date] [Thread] [Top] [All Lists] |