I have been running syslog-ng v1.6.5 for about 6 months with no problems. Its the main syslog process and logs the days traffic to a single messages file, it does a little filtered for selected hosts and forwards them on (w/spoofing) to another device. Just this week, for some unknown reason I've yet to find, syslog-ng reinitializes a new configuration on the hour (just as if it received a HUP) and overwrites the previous hours file. Now I rotate the logs at midnight via cron, there i move the file and kill HUP the syslog-ng process which works fine. remove_if_older is not set in my config so its taking the default. Anyone else ever have unexplained hourly restarts on the syslog-ng process? -= stan ________________________________________________________________ Sent via the WebMail system at mail.ameritel.net --- [This E-mail scanned for viruses by mail.ameritel.net]