Richard Fish wrote:
> I think a far better option would be to filter them in
> /etc/syslog-ng/syslog-ng.conf. Then you do not have to re-patch your
> kernel with every upgrade.
This affects only output via syslog. During the md autorun, the kernel hasn't
even finished booting. The post was about output from dmesg, the kernel
ringbuffer. AFAIK there's no way around a kernel patch.
> I use the following instructions to filter out the "PHY reset until link
> up" messages that I get when eth0 is "up" (required for ifplugd to
> function), but not connected to anything. It can easily be adapted for
> the RAID messages.
>
> # The eth reset messages also bug me...
> filter not_eth_reset {
> not(match("PHY reset until link up"));
> };
>
> log { source(src); filter(not_eth_reset); destination(messages); };
Nice example though. Haven't used syslog filtering by now.
Christoph
--
echo mailto: NOSPAM !#$.'<*>'|sed 's. ..'|tr "<*> !#:2" [EMAIL PROTECTED]
--
gentoo-user@gentoo.org mailing list
