[syslog-ng] [Bug 178] Spoofed source address bug introduced in 3.3.5

bugzilla at bugzilla.balabit.com bugzilla at bugzilla.balabit.com
Wed Jul 11 11:49:11 CEST 2012


--- Comment #14 from Gergely Nagy <algernon at balabit.hu>  2012-07-11 11:49:10 ---
I was about to merge this, and release 3.3.6, but found a regression: if a host cannot be resolved at reload time, the whole whole reload will fail and fall
back to the old, which is not what we want.

I can ignore the return value of resolve_hostname() during afinet_dd_init, since we're using it only for side-effects anyway, but that will mean that if a host
is not resolvable at reload time, then it won't be retried, and the same bug will surface - just less often, and under rare circumstances.

I'm not entirely sure how to fix this new regression.. the best would be if the resolve_hostname() could be moved out of afinet_dd_init, so it wouldn't trigger
during reload, but it would trigger before trying to send anything to the host. That would not only fix the regression introduced by the fix for the other
regression, it would also look a lot better, and less hackish.

Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.

More information about the syslog-ng mailing list