Hi, the parameters you listed are all viable.
But listing them in global() would have no effect. You need to specify them in an action(), ruleset() or main-queue() so they are used there. Disk queues always use the disk and do not buffer anything in memory, which means they are ultra-reliable, but slow. For the best result you should put the queue in front of a reliable transport action such as relp. Regards 2016-12-14 10:42 GMT+01:00 mostolog--- via rsyslog < [email protected]>: > Hi > > Queue documentation improvements are on my TODO list for next year. Until > then, we'll have to ask here in order to properly know how they work. > > Would a configuration like: > > global( > queue.filename="rsyslog.qi" > queue.maxdiskspace="1G" > queue.SaveOnShutdown="on" > queue.type="Disk" > ) > > make any input, action, ruleset...everything to be disk-supported so 100% > reliable? (0 messages lost, although slow) > > Regards > > _______________________________________________ > rsyslog mailing list > http://lists.adiscon.net/mailman/listinfo/rsyslog > http://www.rsyslog.com/professional-services/ > What's up with rsyslog? Follow https://twitter.com/rgerhards > NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad > of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you > DON'T LIKE THAT. > _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com/professional-services/ What's up with rsyslog? Follow https://twitter.com/rgerhards NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE THAT.
