From: "Richard B. Johnson" <root@chaos.analogic.com>
To: Sebastian Piecha <spi@gmxpro.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: How to wait for kernel messages?
Date: Tue, 14 Oct 2003 08:12:10 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.53.0310140804200.19781@chaos> (raw)
In-Reply-To: <3F8ACBEA.5414.1072DA2C@localhost>
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
`cat /proc/kmsg`
...or to wait forever for each message, just open /proc/kmsg and
post a read. Note that kernel logger is also waiting for such
messages so you might not get them all.
Of course the 'Unix-way' is to just do `tail -f /var/log/messages`,
or whatever your log-file name is.
Cheers,
Dick Johnson
Penguin : Linux version 2.4.22 on an i686 machine (797.90 BogoMips).
Note 96.31% of all statistics are fiction.
next prev parent reply other threads:[~2003-10-14 12:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-13 13:59 Sebastian Piecha
2003-10-14 12:12 ` Richard B. Johnson [this message]
2003-10-14 21:07 Jim Keniston
2003-10-14 22:57 ` Sebastian Piecha
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=Pine.LNX.4.53.0310140804200.19781@chaos \
--to=root@chaos.analogic.com \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®