On Wed, 29 Aug 2007 09:37:00 EDT, Peter Staubach said: > There are a lot of ways to discover who is throwing trash > at your system other than the kernel printing messages. > > Tools such as tcpdump and tethereal/wireshark make much better > tools for this purpose. Given the number of times I've had to use tcpdump and wireshark to wade through literally gigabyte traces looking for stuff specifically because the kernel *didn't* printk information it had handy, I'm not too sympathetic. Especially when the printk in question is currently saying "I know who's causing the problem but I'm not going to tell you, nyah nyah".... (And if there's better ways than kernel printing messages, does that mean we should deprecate the iptables '-j LOG' target while we're at it?)
Attachment:
pgpD7m9wms8O3.pgp
Description: PGP signature
- References:
- [PATCH] Add source address to sunrpc svc errors
- From: "Dr. David Alan Gilbert" <[email protected]>
- Re: [PATCH] Add source address to sunrpc svc errors
- From: Randy Dunlap <[email protected]>
- Re: [PATCH] Add source address to sunrpc svc errors
- From: "Dr. David Alan Gilbert" <[email protected]>
- Re: [PATCH] Add source address to sunrpc svc errors
- From: "J. Bruce Fields" <[email protected]>
- Re: [PATCH] Add source address to sunrpc svc errors
- From: [email protected]
- Re: [PATCH] Add source address to sunrpc svc errors
- From: Peter Staubach <[email protected]>
- [PATCH] Add source address to sunrpc svc errors
- Prev by Date: Re: [PATCH 4/5] Net: ath5k, license is GPLv2
- Next by Date: Re: Linux 2.6.23-rc4: BAD regression
- Previous by thread: Re: [PATCH] Add source address to sunrpc svc errors
- Next by thread: Stardom SATA HSM violation
- Index(es):
 |