On 16-08-15 14:01:51, Darren S. wrote: > Hoping to verify expected behavior of unresolvable FQDNs for remote > loghosts in syslog.conf(5). > > *.notice;auth,authpriv,cron,ftp,kern,lpr,mail,user.none > @loghost.example.com > auth,daemon,syslog,user.info;authpriv,kern.debug > @loghost.example.com > > In the above configuration, if loghost.example.com cannot be resolved, > is it expected that syslogd(8) should detect this and log a warning,
If in debug it will warn you. > or exit with an error, or proceed to run normally and simply fail to > log to the remote host? It should proceed normally as you could have it logging to file as well. > > Looking at a case in 5.8 (amd64) where the latter seems to be > happening after the log host was recently updated in DNS with a new > hostname but configuration update was missed on log clients. Wondering > if this is bug or feature (or if I've missed something). > > Regards, > > -- > Darren Spruell > phatbuck...@gmail.com > -- Edgar Pettijohn
