From: Jim Keniston <jkenisto@us.ibm.com>
To: spi@gmxpro.de
Cc: LKML <linux-kernel@vger.kernel.org>, root@chaos.analogic.com
Subject: Re: How to wait for kernel messages?
Date: Tue, 14 Oct 2003 14:07:02 -0700 [thread overview]
Message-ID: <3F8C6576.464328CE@us.ibm.com> (raw)
On Mon, 13 Oct 2003, Sebastian Piecha wrote:
> I have some problems with one NIC. Due to lack of time as an
> workaround I'd like to wait for the kernel message "NETDEV WATCHDOG:
> eth0: transmit timed out" and ifconfig down/up the NIC.
>
> How can I trigger any action by such a kernel message? Do I have to
> grep the kernel log?
>
> Mit freundlichen Gruessen/Best regards,
> Sebastian Piecha
If you had LTC's Event Logging installed, and you had your kernel
configured to forward printk messages to the event log, you could
do something like this:
evlnotify -f 'data~"NETDEV WATCHDOG: eth0: transmit timed out"' \
-a 'ifconfig eth0 down; ifconfig eth0 up'
That would cause the ifconfig down/up to run each time the indicated
printk happened.
Jim Keniston
IBM Linux Technology Center
next reply other threads:[~2003-10-14 21:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-14 21:07 Jim Keniston [this message]
2003-10-14 22:57 ` How to wait for kernel messages? Sebastian Piecha
-- strict thread matches above, loose matches on Subject: below --
2003-10-13 13:59 Sebastian Piecha
2003-10-14 12:12 ` Richard B. Johnson
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=3F8C6576.464328CE@us.ibm.com \
--to=jkenisto@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=root@chaos.analogic.com \
--cc=spi@gmxpro.de \
/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