Could this be worked round in general with a kill -HUP syslog-ng at the end of the "ifup" script for those instances where syslog-ng starts before networking itself? I would imagine this should ensure syslog-ng is "notified" of the "change of state" of the machine, causing it to refresh its IP sockets. In addition a daily HUP to rotate logs should also effectively heal the problem within 24 hours? Ted ************************************************************************************************ This E-mail message, including any attachments, is intended only for the person or entity to which it is addressed, and may contain confidential information. If you are not the intended recipient, any review, retransmission, disclosure, copying, modification or other use of this E-mail message or attachments is strictly forbidden. If you have received this E-mail message in error, please contact the author and delete the message and any attachments from your computer. You are also advised that the views and opinions expressed in this E-mail message and any attachments are the author's own, and may not reflect the views and opinions of FLEXTECH Television Limited. ************************************************************************************************