I think the easiest fix would be to get syslog-ng to put its 'syslog-ng.pid' file in the '/var/run' directory. What is in syslog.conf (or syslog-ng.conf)? Use 'man syslog.conf' or something similar to divine wether there is a configuration setting that can force the 'syslog-ng.pid' file to be in '/var/run'. Another option whould be to check /etc/rc.d/init.d/syslog (or /etc/rc.d/init.d/syslog-ng) to see if the creation of the 'syslog-ng.pid' is controllable from there. Good luck, Troy >>> simeonuj at eetc.com 04/09/01 03:30PM >>> I am trying to rotate my logs but am having problems with logrotate. This is the command used. /var/log/logfile { postrotate /usr/bin/killall -HUP `cat /var/run/syslog-ng.pid` endscript } The problem with this is that the syslog-ng.pid file seems to be generated in whatever directory you started syslog-ng from instead of /var/run/*. Is this a configuration problem of the system? If a system problem how do I go about fixing it? Is there a simpler way to send an HUP signal? I am using Redhat-6.2 on an ALPHA with syslog-ng 1.4.11. I already posted this to another list but they havn't responded. The list server might be down or something because I havn't received anything from them for quite some time. Can anyone help me? sim _______________________________________________ tclug-list mailing list tclug-list at mn-linux.org https://mailman.mn-linux.org/mailman/listinfo/tclug-list