On Tue, Aug 07, 2001 at 05:11:31PM -0700, Jay Soffian wrote:
I haven't tracked this down yet, but it appears that when you send syslog-ng a SIGHUP while it is running with '-v', it terminates instead of restarting.
hmm.. it should no that, and it doesn't here: balabit:~/src/syslog-ng-1.5/src$ ./syslog-ng -dvf syslog-ng.conf binding fd 3, inetaddr: 0.0.0.0, port: 1999 io.c: listening on fd 3 syslog-ng version 1.5.8 starting [1]+ Stopped ./syslog-ng -dvf syslog-ng.conf balabit:~/src/syslog-ng-1.5/src$ bg [1]+ ./syslog-ng -dvf syslog-ng.conf & balabit:~/src/syslog-ng-1.5/src$ ps PID TTY TIME CMD 28526 pts/7 00:00:00 bash 10468 pts/7 00:00:00 syslog-ng 10469 pts/7 00:00:00 ps balabit:~/src/syslog-ng-1.5/src$ kill -HUP 10468 balabit:~/src/syslog-ng-1.5/src$ SIGHUP received, restarting syslog-ng balabit:~/src/syslog-ng-1.5/src$ balabit:~/src/syslog-ng-1.5/src$ fg ./syslog-ng -dvf syslog-ng.conf [1]+ Stopped ./syslog-ng -dvf syslog-ng.conf balabit:~/src/syslog-ng-1.5/src$ fg ./syslog-ng -dvf syslog-ng.conf Marking fd 3 for closing. Closing fd 3. binding fd 3, inetaddr: 0.0.0.0, port: 1999 io.c: listening on fd 3 new configuration initialized -- Bazsi PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1