Stop start issue with slackware

[Brent Kennedy <br...@cfl.rr.com>]

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.

I have a script that needs to send a reload to spamd so it can load in new
rules once a week.

Any suggestions?

Thanks

-Brent

Bayes mysql PHP report

[Brent Kennedy <br...@cfl.rr.com>]

Does anyone have or know where to get a web report for the bayes db in
mysql?

Thanks

-Brent

RE: Stop start issue with slackware

[Robert - eLists <li...@abbacomm.net>]

> 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.
> I have a script that needs to send a reload to spamd so it can load in new
> rules once a week.
> Any suggestions?
> Thanks
> -Brent

Brent,

You might consider another way for the script to do it like

Setup and otherprocessing goes here

/etc/init.d/spamassassin restart

Error checking and other processing goes here

Or something to that effect for your distro

 - rh

Re: Stop start issue with slackware

["Daryl C. W. O'Shea" <sp...@dostech.ca>]

Brent Kennedy wrote:
> Dooh
>  
> Did they fix this in 3.2.1? 

No, but as Theo mentioned, using a PID file is your best bet anyway.

Daryl

RE: Stop start issue with slackware

[Brent Kennedy <br...@cfl.rr.com>]

Dooh
 
Did they fix this in 3.2.1? 

-----Original Message-----
From: Daryl C. W. O'Shea [mailto:spamassassin@dostech.ca] 
Sent: Monday, June 11, 2007 5:26 PM
To: Brent Kennedy
Cc: 'SpamAssassin'
Subject: Re: Stop start issue with slackware

Brent Kennedy wrote:
> 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.

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?

You could revert the change from r490760 or you could just stop then 
start spamd rather than HUP'ing it.

See http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5419 for more 
info.


Daryl

Re: Stop start issue with slackware

[Theo Van Dinter <fe...@apache.org>]

On Mon, Jun 11, 2007 at 05:25:51PM -0400, Daryl C. W. O'Shea wrote:
> You could revert the change from r490760 or you could just stop then 
> start spamd rather than HUP'ing it.

Or as it came up in the irc channel, use a pid file (see "man spamd") and then
you don't care what the process calls itself.

-- 
Randomly Selected Tagline:
I'd love to, but I'm staying home to work on my cottage cheese.

Re: Stop start issue with slackware

["Daryl C. W. O'Shea" <sp...@dostech.ca>]

Brent Kennedy wrote:
> 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.

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?

You could revert the change from r490760 or you could just stop then 
start spamd rather than HUP'ing it.

See http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5419 for more 
info.


Daryl