SA Bugzilla – Bug 3910
[review] slackware rc.d script fails
Last modified: 2004-10-20 00:33:52 UTC
the rc.d script provided for slackware fails to stop (and restart) spamd. for this to work here, I had to change the 'stop' method from # $KILL -9 `cat $PIDFILE` # /bin/rm $PIDFILE to $KILL `/sbin/pidof $PNAME` and on the 'restart' method, I added a 'sleep 1s' between stop and start
I tested this on a Slackware 10 box. The script dies on line 41, "/bin/rm $PIDFILE" because spamd seems to unlink its pid file when it is killed. Also, spamd was leaving zombie children when killed with a SIGKILL. I changed the signal that kill sends to spamd and added the -f flag to rm. I also did a bit of cosmetic cleanup.
Created attachment 2465 [details] Patch to fix slackware init script
+1 on Henry's patch I don't think we need the author tag, though. ;-)
+1 sure.
I tested the patch on my production server, and it seems to work fine. I'm new to bugzilla. As the bug submitter, do I have to take any action? Checking this 'Resolve bug, changing resolution to FIXED' bellow, for instance?
Subject: Re: [review] slackware rc.d script fails On Tue, Oct 19, 2004 at 12:02:48PM -0700, bugzilla-daemon@bugzilla.spamassassin.org wrote: > I'm new to bugzilla. As the bug submitter, do I have to take any action? > Checking this 'Resolve bug, changing resolution to FIXED' bellow, for instance? No, one of the developers will apply the patch to the code, then close the ticket when that's complete. bug submitters pretty much only ever close a bug if they figure out that what they reported wasn't a bug (pebkac or whatever...)
Committed patch to stable and head.