05.11.2013 19:26, Rainer Gerhards:
Because this again requires code to be maintained for a border case. As I said, I wouldn't wonder if you get a segfault under some configurations where this is set to one (e.g. all watermarks are 0 in this case).
Nobody has complained yet, right? Maybe it will break, maybe not. If the problem is in watermarks, then it is not a problem of queue size.
Btw, I've just tested it - and it works.
I *really* don't see any valid use case for a queue with size 1... What is it? We were just about direct mode. Size 1, assuming it works, is essentially direct mode with a lot of overhead. So use direct in this case. Does that sound like an undue restriction?
No, it is not the same as direct queue. In async queue, you can drop messages when the queue is full (even if it's size is 1). In direct mode, you must process all the messages.
As of today, I do not have a real use case for this configuration. But it can be used, for example, to deliver *some* of messages to a very slow output with minimum delay. You can even deliver a sample of message each 1 second.
-- Pavel Levshin _______________________________________________ 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.
