On Thu, Jul 3, 2014 at 4:58 PM, user01 <[email protected]> wrote: > > Hi > > On Wed, 2 Jul 2014 22:59:03 -0700 (PDT) > David Lang <[email protected]> wrote: > > > > > even with drop a failover should work > > Dropping a packet via paketfilter still leaves arp-resolution intact. > Therefore > intermediate routers (or your log-client) will not generate a "host > unreachable" > or something similar. It would be up to the associated tcp-client > (rsyslogd in this > case) to detect subsequent connection failures
what rsyslog does is pretty straightforward: it uses the regular (socket) API calls and expects the OS to return an error if there is one. So I conclude the OS also does not know this connection is broken. Rainer > and flag an error. Your OS can`t do > anything about this situation. > Maybe dropping arp-resolution for that particular client or server could > simulate an > more accurate "syslog-server has died"? :) > > Regards > user01 > _______________________________________________ > 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. > _______________________________________________ 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.
