From: Henrik Nordstrom <[EMAIL PROTECTED]>
> The most obvious way is to get rid of the cause. For example by
> installing a small hub where the laptop can connect ...
I wouldn't need the bridge in this case...
> Another way to get rid of this is to lessen the amount of kernel
> logging in your syslog.conf. (...)
> Problem is that by doing this you may loose other messages you
> consider important.
Exactly.
> A thrid way is to patch your kernel to not log these messages.
This sounds good. Do you have a more detailed solution on this?
> A fourth way is to use a "smart" syslog daemon that can act on
> message content, not only on facility and priority, thus allowing
> you to filter out the exact messages only.
What smart syslogd do you use? - But anyway, I don't want my machine
to produce and throw away these messages night and day...
> Or fifth, accept that these get logged, and just ignore them while
> reading your kernel logs ("grep -v" is your friend)
It's not just filling my logs with useless information and my hard
disk with useless logs, it also makes constant noises because of the
syncing from syslogd! That makes me nervous.
Regards,
Robert
_______________________________________________
Bridge mailing list
[EMAIL PROTECTED]
http://www.math.leidenuniv.nl/mailman/listinfo/bridge
