should have read: queue *info* file (.qi)
> -----Original Message----- > From: [email protected] [mailto:rsyslog- > [email protected]] On Behalf Of Rainer Gerhards > Sent: Wednesday, November 17, 2010 6:15 PM > To: rsyslog-users > Subject: Re: [rsyslog] dealing with broken spool > > There is a dedicated setting (checkpoint interval or so) to set how > often the > queue file should be written. It's explained in the queue doc. > > > -----Original Message----- > > From: [email protected] [mailto:rsyslog- > > [email protected]] On Behalf Of Marcin Miroslaw > > Sent: Wednesday, November 17, 2010 6:11 PM > > To: [email protected] > > Subject: Re: [rsyslog] dealing with broken spool > > > > Supplement: > > Rsyslog was looking for dbq.00000097 (this was writtent in dbq.qi), I > > touched dbq.00000097 and all queue was relayed to the next rsyslog. > > Zeros wasn't problematic. So question could be written now as: "Why > > dbq.qi has incorrect information about oldest file? or Was the oldest > > file deleted by fsck?" > > I'd like to ask another question, about configuration this time. > > I'm not sure about meanings parameters: > > $MainMsgQueueLowWaterMark and $MainMsgQueueHighWaterMark . Could them > > be > > usefull to have queue more often flushed to disk? For example if i > set: > > $MainMsgQueueLowWaterMark 3 > > $MainMsgQueueHighWaterMark 8 > > should queue workes flush to 5 messages to disk, if number of > messages > > in memory reach value 8? > > > > > > _______________________________________________ > > 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
