I believe Peter is correct, it does not seem that a HUP causes
connection reset.
[root@pogo ~]# ss -tupn | grep 10.14
tcp ESTAB 0 0 192.168.10.13:35336
192.168.10.14:5147 users:(("rsyslogd",pid=833,fd=54))
tcp ESTAB 0 0 192.168.10.13:45890
192.168.10.14:5141 users:(("rsyslogd",pid=833,fd=51))
tcp ESTAB 0 0 192.168.10.13:43708
192.168.10.14:5145 users:(("rsyslogd",pid=833,fd=56))
[root@pogo ~]# kill -HUP 833
[root@pogo ~]# ss -tupn | grep 10.14
tcp ESTAB 0 0 192.168.10.13:35336
192.168.10.14:5147 users:(("rsyslogd",pid=833,fd=54))
tcp ESTAB 0 0 192.168.10.13:45890
192.168.10.14:5141 users:(("rsyslogd",pid=833,fd=51))
tcp ESTAB 0 0 192.168.10.13:43708
192.168.10.14:5145 users:(("rsyslogd",pid=833,fd=56))
A true connection reset would request and get a different ephemeral
sending port for each connection, and as above this did not happen.
Regards,
On 6/1/20 3:13 AM, Peter Viskup via rsyslog wrote:
Just to make a note.
On Sat, May 30, 2020 at 8:05 PM David Lang via rsyslog <
[email protected]> wrote:
when you issue a HUP, rsyslog creates new connections.
This does not seems to be right. AFAIK the re-opening omfwd connections was
not implemented or am I wrong?
Peter
_______________________________________________
rsyslog mailing list
https://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.
_______________________________________________
rsyslog mailing list
https://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.
