> Is that the expected behavior of rsyslog with that configuration ? I believe it is. http://www.rsyslog.com/doc/queues.html
> How can we configure the TCP action in order to prevent the complete > locking ? http://www.rsyslog.com/doc/rsyslog_reliable_forwarding.html beside what's written there, this is my setup which I'm very fine with: #forward1 $ActionQueueType LinkedList # use asynchronous processing $ActionQueueFileName srvrfwd1 # set file name, also enables disk mode $ActionResumeRetryCount -1 # infinite retries on insert failure $ActionQueueSaveOnShutdown on # save in-memory data if rsyslog shuts down $ActionQueueMaxDiskSpace 100m # limit disk cache $ActionQueueTimeoutEnqueue 100 # dont block worker indefinitely when cache *.* @@loghost:515 _______________________________________________ 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.
