Hello, Thanks for all the informations.
>> 2. Will be the adress based bind feature also in the future available for >> imtcp? (Thats my big wish and hope) ;) > >Add a tracker to github.Makes sense, but the todo list is very long. >Not likely to happen within the next three month to set an >expectation, but you never know. I placed: https://github.com/rsyslog/rsyslog/issues/277 regards Chris Gesendet: Dienstag, 17. März 2015 um 12:13 Uhr Von: "Rainer Gerhards" <[email protected]> An: rsyslog-users <[email protected]> Betreff: Re: [rsyslog] imptcp vs imtcp - TCP Syslog Interface binds vs. performance 2015-03-11 11:42 GMT+01:00 <[email protected]>: > Hallo list, > > I have to setup a solution using rsyslog and TCP syslog sources. > Therefore I made some tests using tmptcp and imtcp especially focusing on > "dying" tcp connections. > > I realized, that imtcp does much more efficient handle death connections > compared to imptcp. > With imtcp they are dying after expiration, as expected, can also be seen in > logfile: > rsyslogd-2165: netstream session 0x9111ff0 from xx.xx.xx.xx will be closed > due to error [v8.8.0 try http://www.rsyslog.com/e/2165 ] > > Unfortunately imtcp does not support address based bind, so it always binds > to 0.0.0.0:[port] > But imptcp does support interface based binds. > > > Now to my questions: > 1. Will imptcp replace in near future imtcp? no > 2. Will be the adress based bind feature also in the future available for > imtcp? (Thats my big wish and hope) ;) Add a tracker to github.Makes sense, but the todo list is very long. Not likely to happen within the next three month to set an expectation, but you never know. > 3. I noticed that compared between imptcp and imtcp the configuration happens > on different levels (modul-load vs input). may be, if so that's just history. imptcp is much more modern. > 4. Why does the "death-connection-handling" is so different in imptcp? probably different contributions or requests. Note that contributions are always very welcome. If this is a business case, you may want to consider Adiscon's support services. There are many more resources available for support customers, it's not just me (if it is me, I am usually able to shuffle some other work to co-workers). Rainer > > > > My configuration with imtcp: > module(load="imtcp" KeepAlive="on" KeepAlive.Probes="1" > KeepAlive.Interval="2" KeepAlive.Time="20") > input(type="imtcp" port="314") > > Configuration with imptcp: > module(load="imptcp") > input(type="imptcp" port="314" keepalive="on" KeepAlive.Probes="1" > KeepAlive.Interval="2" KeepAlive.Time="20") > > Best regards, > Chris > > > _______________________________________________ > rsyslog mailing list > http://lists.adiscon.net/mailman/listinfo/rsyslog[http://lists.adiscon.net/mailman/listinfo/rsyslog] > http://www.rsyslog.com/professional-services/[http://www.rsyslog.com/professional-services/] > What's up with rsyslog? Follow > https://twitter.com/rgerhards[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://lists.adiscon.net/mailman/listinfo/rsyslog] http://www.rsyslog.com/professional-services/ What's up with rsyslog? Follow https://twitter.com/rgerhards[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.
