I am also having problems sending 1.4.11 the HUP signal. Seems to die if it is sent more than once. Doesn't reload the config properly. I think you may be right about the file handles. I asked for help about this a while ago but no one seems to know what the problem is/Don't care. sim Adrian Chung wrote:

Hi all, I'm noticing some strange behaviour with syslog-ng 1.4.11 and libol 0.2.21.

I've got named running in a chroot'd environment, with it's own /var/named/dev/log. Syslog-ng is configured to use both /dev/log and /var/named/dev/log as unix-stream sources, with output going to /var/daemon.log.

When I logrotate the /var/log/daemon.log file, logging from named completely stops. It doesn't appear anywhere. Even after sending HUP signals to both named and syslog-ng.

The only way that logging resumes is if I completely kill and restart syslog-ng.

Seems like syslog-ng isn't flushing it's file handles?

-- Adrian Chung - adrian@enfusion-group.com http://www.enfusion-group.com/~adrian 1:23pm up 75 days, 19:21 - [rogue.enfusion-group.com]

_______________________________________________ syslog-ng maillist - syslog-ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng