RE: Stop start issue with slackware
Did they fix this in 3.2.1?
From: Daryl C. W. O'Shea [mailto:firstname.lastname@example.org]
Sent: Monday, June 11, 2007 5:26 PM
To: Brent Kennedy
Subject: Re: Stop start issue with slackware
Brent Kennedy wrote:[color=blue]
> I just upgraded to 3.2.0 from 3.1.7 and now when I send:
> "killall -HUP spamd"
> It just says: "spamd: no process killed"
> But, when I do a ps -ef, there is a spamd and two child processes.
> This worked fine in 3.1.7, so I don't know what changed in 3.2 to make
> it more resistant to killall.[/color]
A change was made to make the buildbots work better. The big downside is it
breaks HUP'ing spamd.
> I have a script that needs to send a reload to spamd so it can load in new
> rules once a week.
> Any suggestions?[/color]
You could revert the change from r490760 or you could just stop then
start spamd rather than HUP'ing it.
See [url]http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5419[/url] for more