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?
2. Will be the adress based bind feature also in the future available for
imtcp? (Thats my big wish and hope) ;)
3. I noticed that compared between imptcp and imtcp the configuration happens
on different levels (modul-load vs input).
4. Why does the "death-connection-handling" is so different in imptcp?
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://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.
