On Tue, 15 Apr 2014, Michael Biebl wrote: > > Actually, yes. This is expected. If you don't have a consumer on > /dev/xconsole (which I assume you don't have), the pipe will run > full eventually and rsyslog will suspend trying to write to the > pipe. It does retry after a while though.
Alright. Got it. > What was fixed was the incorrect way to detect failures when writing > to the pipe. So rsyslog continuously retried without actually > suspending properly. I see. > If you want to suppress those log messages completely, you can set > action.reportSuspension [0] to off. Either globally or per output. > > Does that sufficiently answer your question? Yes. Thanks. > [0] http://www.rsyslog.com/doc/global.html The other option may be to comment out the xconsole rule in rsyslog.conf: --- /etc/rsyslog.conf.orig 2012-03-15 13:39:12.000000000 +0100 +++ /etc/rsyslog.conf 2014-04-15 12:47:11.000000000 +0200 @@ -115,7 +115,7 @@ # NOTE: adjust the list below, or you'll go crazy if you have a reasonably # busy site.. # -daemon.*;mail.*;\ - news.err;\ - *.=debug;*.=info;\ - *.=notice;*.=warn |/dev/xconsole +#//#daemon.*;mail.*;\ +#//# news.err;\ +#//# *.=debug;*.=info;\ +#//# *.=notice;*.=warn |/dev/xconsole Wouldn't it? As I know I don't have a consumer on /dev/xconsole. Would you agree? Cheers, -- Cristian -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
