Scott Griffith, ISES-LLC wrote:
On Oct 6, Mark Edwards wrote:
I'm having a problem starting spamd via sudo. This is using the current
FreeBSD port, and the behavior started with SA 2.6. I can start it
successfully if I su to root, but if I try to use sudo, I get:
sudo
I'm having a problem starting spamd via sudo. This is using the current
FreeBSD port, and the behavior started with SA 2.6. I can start it
successfully if I su to root, but if I try to use sudo, I get:
sudo /usr/local/etc/rc.d/spamd.sh start
Insecure directory in $ENV{PATH} while running with
Date: Tue, 30 Sep 2003 15:58:44 -0400
From: Scott Rothgaber <[EMAIL PROTECTED]>
Organization: Palmetto Network Solutions, Ltd
To: [EMAIL PROTECTED]
Subject: Re: [SAtalk] Re: Restart Spamd
Malte S. Stretz wrote:
> kill -HUP should work with SpamAssassin 2.60 under Perl 5.6.1 and up
From: "Hannu Liljemark" <[EMAIL PROTECTED]>
Date: Sun, 28 Sep 2003 10:18:48 +0300
To: [EMAIL PROTECTED]
Subject: Re: [SAtalk] SIGHUP crashing spamd in 2.60
On Sat, Sep 27, 2003 at 03:21:32PM -0700, Mark Edwards wrote:
> Anyone else not able to SIGHUP
I was excited to see the addition of SIGHUP functionality in 2.60.
Unfortunately, while spamd seems to receive and obey the signal:
Sep 27 15:15:50 lilbuddy spamd[47851]: server hit by SIGHUP, restarting
spamd dies shortly thereafter.
I'm running the port on FreeBSD 4.8p10.
I do have the razo