we use syslog-ng in a large cluster of some online services. however we do encounter problems with the pid-file handling.
i start syslog-ng as
syslog-ng --pidfile=/var/run/syslog-ng.pid --cfgfile=/usr/global/etc/syslog-ng.conf
and its running fine.
yesterday i did: # ps auxw| grep syslog-ng root 5366 ...syslog-ng --pidfile=/var/run/syslog-ng.pid... # cat /var/run/syslog-ng.pid 5366
today i did: # ps auxw| grep syslog-ng root 18357 ...syslog-ng --pidfile=/var/run/syslog-ng.pid... # cat /var/run/syslog-ng.pid 5366
so for some mysterious reasons a) syslog-ng restarts (maybe some cron job to logrotate the systems syslog) b) the pid in /var/run/syslog-ng.pid does not get updated
syslog-ng is running here on Tru64 4.0 alpha.
is syslog-ng running as root? it may not have all the privileges to create the pidfile. pidfile is created only if syslog-ng is not started with -d. -- Bazsi PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1 url: http://www.balabit.hu/pgpkey.txt