Am 30.07.2010 14:52, schrieb Steffen Sledz: > If a module always returns RS_RET_OK (like ompipe does) the actionDoRetry > loop may not have leaved faked ACT_STATE_SUSP state in case iResumeOKinRow > had ever reached a count of 1000.
In our test the suggested patch seems to fix this problem. :) But now we hit the next one. :( If we use a LinkedList DA-Queue for this channel suspended messages may be transmitted out-of-order. This may not be a problem for database consumers. But in our context this is really bad. Is this a bug or an intended behaviour? Is it possible to force strict order of messages? Steffen _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com
