[syslog-ng] fails if dns error resolvehostnamedestinationforwarding

[Balazs Scheidler]

On Wed, 2008-11-12 at 12:12 -0800, JV wrote:
> I don't expect syslog-ng to resolve a name when its not in dns or hosts but i expect syslog-ng to still start & run as it has other filter rules saying it needs to log to local files.
> 
> 
> Use case is when a system reboots syslog-ng starts up before network is fully up on the host, syslog-ng won't start and no local logging takes place either. 
> 
> We're talking UDP here , so no reason syslog-ng can't keep trying to resolve and send new lines when needed once network connectivity is working and name resolution is complete.
> Isn't that how the OS native "syslog" works ?

syslog-ng 2.1 has support for retrying the connection after start-up,
but I didn't backport it to 2.0 as it would be too risky. Please try
2.1, it should work in this case too.

-- 
Bazsi