Under the circumstances below, syslogd stops sending data to a remote, central logging server:
* If the destination cannot be resolved via DNS etc on start up * If the central logging server becomes unavailable * There is a network interruption between the syslogd host and the central logging server This is using UDP 514 as the transport. The only way to fix this issue is by restarting the syslogd daemon (rcctl restart syslogd). Sending a HUP will not force it to reflow. Is this the expected behaviour of syslogd or is this a bug that requires further investigation? This occurs on syslogd hosts of 6.7 to 6.9 flavours. Thanks, Jason.
