The implementation appears to use one TCP session for each rule which forwards messages. Apparently in 6 (not yet stable) there is upcoming functionality to dump all these into a single queue and forward that one queue over a single connection.
That said, a cost of one TCP connection per rule really isn't that high, and does ensure that if one rule gets spammed to death the others can still deliver. On Apr 23, 2012, at 11:39 AM, [email protected] wrote: > we are using rsyslog on our clients to forward syslog to a syslog-ng server > over a tcp port.. when I look on the server, I > may see anywhere from 1 to 6 ESTABLISHED tcp sessions from each rsyslog > client.. > Ive been searching but cant seem to find a reason why there would be multiple > connections from each client. Can anyone > shed some light on why that would be? we are trying to gauge the appropriate > number of tcp connections we should allow on > the server. > > thanks/regards, > Jason > > _______________________________________________ > 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 -- Jo Rhett Net Consonance : consonant endings by net philanthropy, open source and other randomness _______________________________________________ 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
