Robert Siemer wrote:
> > 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?
Find the error messages and comment them out. Then rebuild your kernel.
> > 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...
I don't use one, but have seen them. Think I first saw this in syslog-ng
<http://freshmeat.net/projects/syslog-ng/>
> > 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.
Understandable.
--
Henrik Nordstrom
MARA Systems AB
Sweden
_______________________________________________
Bridge mailing list
[EMAIL PROTECTED]
http://www.math.leidenuniv.nl/mailman/listinfo/bridge
