Luke Mewburn wrote :
| Anthony provided a suggested patch, which I'm a bit leery to
| incorporate because it would cause syslogd to attempt to look
| up an unknown host name each time a message was attempted to be
| forwarded to a host with an unknown name. This could result in
| pathological behaviour and unexpected delays in logging waiting for
| hostname lookups.

A host that does not exist is likely to be an error, so the weird
behaviors you mention should not happen. And once the host is found for
the first time, the look ups stop immediately, so...

But I agree on the fact that my proposed patch can result in a bad
behavior in certain circumstances.

| A simpler solution would be for Anthony to install a script which
| forced syslogd to reload its config file after named started.
| Something like the following (untested and not perfect) script
| installed as /etc/rc.d/reloadsyslogd might help:
| 
| 	#!/bin/sh
| 	# PROVIDE: reloadsyslogd
| 	# REQUIRE: named
| 	# BEFORE: DAEMON
| 
| 	. /etc/rc.subr
| 	name="reloadsyslogd"
| 	start_cmd="/etc/rc.d/syslogd reload"
| 	stop_cmd=":"


Actually it should be enough and simpler for me to put a
 "/etc/rc.d/syslogd reload" in rc.local.