http://bugzilla.spamassassin.org/show_bug.cgi?id=3625
------- Additional Comments From [EMAIL PROTECTED] 2004-08-02 09:15 ------- i've done a little more testing on this and have found out the following. - spamd will log properly if the syslog socket goes away... however - spamd doesnt seem to take a TERM signal properly. See below.. restarting syslog and then sending a TERM signal via daemontools never takes down spamd. [EMAIL PROTECTED] service]# /etc/init.d/syslog restart Shutting down kernel logger: [ OK ] Shutting down system logger: [ OK ] Starting system logger: [ OK ] Starting kernel logger: [ OK ] [EMAIL PROTECTED] service]# svstat spamd spamd: up (pid 15610) 32 seconds [EMAIL PROTECTED] service]# svc -d spamd [EMAIL PROTECTED] service]# svstat spamd spamd: up (pid 15610) 40 seconds, want down [EMAIL PROTECTED] service]# svstat spamd spamd: up (pid 15610) 146 seconds, want down [EMAIL PROTECTED] service]# echo | spamc X-Spam-Score: -1.4 X-Spam-Flag: NO [EMAIL PROTECTED] service]# svstat spamd spamd: up (pid 15610) 174 seconds, want down [EMAIL PROTECTED] service]# ps axw | grep spamd 6989 ? S 0:00 supervise spamd 15610 ? S 0:02 /usr/bin/perl -T -w /usr/bin/spamd -q -x -m 4 15644 ? S 0:00 spamd child 15645 ? S 0:00 spamd child 15646 ? S 0:00 spamd child 15647 ? S 0:00 spamd child [EMAIL PROTECTED] service]# kill -9 15610 [EMAIL PROTECTED] service]# ps axw | grep spamd 6989 ? S 0:00 supervise spamd 15644 ? S 0:00 spamd child 15645 ? S 0:00 spamd child 15646 ? S 0:00 spamd child 15647 ? S 0:00 spamd child [EMAIL PROTECTED] service]# kill -9 15644 [EMAIL PROTECTED] service]# kill -9 15645 [EMAIL PROTECTED] service]# kill -9 15646 [EMAIL PROTECTED] service]# kill -9 15647 [EMAIL PROTECTED] service]# svstat spamd spamd: down 15 seconds, normally up [EMAIL PROTECTED] service]# svc -u spamd [EMAIL PROTECTED] service]# svstat spamd spamd: up (pid 17282) 2 seconds If I send a HUP after restarting syslogd, it will restart. Or, If i send a HUP after a down, it will take the service down. But svc -t and svc -d do nothing after a syslogd restart. [EMAIL PROTECTED] service]# svc -u spamd [EMAIL PROTECTED] service]# svstat spamd spamd: up (pid 21131) 1 seconds [EMAIL PROTECTED] service]# /etc/init.d/syslog restart Shutting down kernel logger: [ OK ] Shutting down system logger: [ OK ] Starting system logger: [ OK ] Starting kernel logger: [ OK ] [EMAIL PROTECTED] service]# svc -d /service/spamd [EMAIL PROTECTED] service]# svstat spamd spamd: up (pid 21131) 12 seconds, want down [EMAIL PROTECTED] service]# svc -h /service/spamd [EMAIL PROTECTED] service]# svstat spamd spamd: down 0 seconds, normally up so the issue is not with how the logging facility fails over, but how spamd handles signals after the log socket is broken. at least that is what i'm seeing... d ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
