You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by Jean-Paul Natola <jn...@familycareintl.org> on 2007/06/12 20:50:10 UTC

RE: HELP!!! SA timing out after 3.2 upgrade-FIXED

Sorry all 

I just panicked -

I didn't know that upgrading would replace my startup script - So I just
added the arguments back into the startup script.



-----Original Message-----
From: Jean-Paul Natola [mailto:jnatola@familycareintl.org] 
Sent: Tuesday, June 12, 2007 2:41 PM
To: users@spamassassin.apache.org
Subject: HELP!!! SA timing out after 3.2 upgrade

Hi all

I just upgraded to 3.2 
Now every message is timing out-

If anyone has any ideas  can you CC me at jnatola@hotmail.com

As no messages are coming in THANKS









Jean-Paul Natola
Network Administrator
Information Technology
Family Care International
588 Broadway Suite 503
New York, NY 10012
Phone:212-941-5300 xt 36
Fax:  212-941-5563
Mailto: Jnatola@Familycareintl.org

Re: HELP!!! SA timing out after 3.2 upgrade-FIXED

Posted by Kris Deugau <kd...@vianet.ca>.
Jean-Paul Natola wrote:
> I didn't know that upgrading would replace my startup script - So I just
> added the arguments back into the startup script.

Most distro packages include a place for you to put startup options that 
override the default ones, and don't get overwritten on upgrades.  This 
includes any of the third-party packages I know of, too.

On most RedHat-ish systems, this is /etc/sysconfig/<daemon name>.

On most Debian-ish systems, this is /etc/default/<daemon name>.

It's usually not a good idea to modify the init scripts directly on any 
system that has a package manager installing prepackaged files.

I can't speak for any other systems or install methods.

-kgd

RE: HELP!!! SA timing out after 3.2 upgrade-NOT

Posted by Jean-Paul Natola <jn...@familycareintl.org>.


Sorry all 

I just panicked -

I didn't know that upgrading would replace my startup script - So I just
added the arguments back into the startup script.



-----Original Message-----


Now that I added the arguments back to my startup script  for SA my CPU usage
is getting nailed


43 processes:  4 running, 39 sleeping
CPU states: 97.3% user,  0.0% nice,  1.2% system,  1.6% interrupt,  0.0% idle
Mem: 146M Active, 52M Inact, 95M Wired, 15M Cache, 60M Buf, 185M Free
Swap: 231M Total, 2952K Used, 228M Free, 1% Inuse