I am not sure if it actually is the same issue, but I would definitely like to get feedback if the patch resolves the situation.
Rainer > -----Original Message----- > From: [email protected] [mailto:rsyslog- > [email protected]] On Behalf Of Todd Michael Bushnell > Sent: Thursday, March 31, 2011 5:54 AM > To: rsyslog-users > Subject: Re: [rsyslog] buffer file not flushed > > Rodney, > > I discovered this a few weeks ago and filed a bug that has since been > acted upon. Rainer responded with a patch, but I've not yet had time > to test. Long story short: it's a known issue that will be resolved in > the near future. > > http://bugzilla.adiscon.com/show_bug.cgi?id=241 > > todd > > > > > On Mar 30, 2011, at 7:13 PM, Rodney McKee wrote: > > > I the simple setup I have the following: > > > > *.*;local0.none @@log1 > > $ActionExecOnlyWhenPreviousIsSuspended on > > & @@log2 > > & /var/spool/rsyslog-buffer > > $ActionExecOnlyWhenPreviousIsSuspended off > > > > When testing a complete failure the rsyslog-buffer file is used, so > all good. But the contents are not flushed from the buffer after the > connection is re-established. > > Should I be doing something different (use relp) to ensure the buffer > is flushed? > > > > Thanks in advance > > Rodney McKee > > _______________________________________________ > > rsyslog mailing list > > http://lists.adiscon.net/mailman/listinfo/rsyslog > > http://www.rsyslog.com > > _______________________________________________ > rsyslog mailing list > http://lists.adiscon.net/mailman/listinfo/rsyslog > http://www.rsyslog.com _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com
