Len,
I hate to imply you didn't cover the basics
probably in order. :))
, but are you sure that newsyslog is sending the HUP to the right PID?
from man newsyslog on freebsd 4.5: path_to_pid_file This optional field specifies the file name to read to find the daemon process id. If this field is present, a signal_number is sent the process id contained in this file. This field must start with "/" in order to be recognized properly. signal_number This optional field specifies the signal number will be sent to the daemon process. By default a SIGHUP will be sent. I will explicitly add the path_to_pid_file to the newsyslog line also, rc.conf now takes params : syslogd_enable (bool) If set to ``YES'', run the syslogd(8) daemon. syslogd_program (str) Path to syslogd(8) (default /usr/sbin/syslogd). syslogd_flags (str) If syslogd_enable is set to ``YES'', these are the flags to pass to syslogd(8). and I have rc.conf with: syslogd_program="/usr/local/sbin/syslog-ng" syslogd_flags="" /var/run/syslog-ng.pid does exist
Maybe it's trying to 'kill -HUP `cat /var/run/syslogd.pid' when the PID file is /var/run/syslog-ng.pid?
here's me at 3 and 8 today, in /var/log/messages, aka, freebsd syslog: Feb 14 11:00:00 buzzard newsyslog[929]: logfile turned over Feb 15 03:13:38 buzzard syslog-ng[357]: new configuration initialized Feb 15 03:18:48 buzzard syslog-ng[357]: SIGHUP received, restarting syslog-ng Feb 15 03:18:48 buzzard syslog-ng[357]: new configuration initialized Feb 15 03:19:37 buzzard syslog-ng[3575]: syslog-ng version 1.4.14 starting Feb 15 08:00:29 buzzard syslog-ng[4342]: syslog-ng version 1.4.14 starting these sighups were cmd line, and they worked: killall -HUP syslog-ng
I don't know how FreeBSD HUPs the syslog daemon, but it could be something like this.
I've added -v to newsyslog's crontab line. we'll see... thanks, Len