On Thu, Jun 20, 2002 at 02:14:34PM -0700, Michelle Brownsworth wrote:
> I've -HUP'ped spamd every time local.cf has been modified. But just
> for grins I killed it completely and restarted it. It came up for a
> short while then died. Odd, I thought. I restarted it again with
> the same result. So figuring it was time to upgrade to the latest
> version, I downloaded 2.31 and installed it.
HUPping spamd won't do anything for you, you have to fully stop/start it.
In fact, sending it a HUP causes it to die because there's no handler
for it.
> [ -x /usr/bin/spamd ] && /usr/bin/spamd -d -F 1 && echo -n ' spamd'
>
> Again it ran briefly (until it was invoked by spamc, I think) then
> died. Seeking more information, I added a "-D" switch for debugging,
> and restarted spamd. This time it stayed running when it was invoked
> by spamc, with these entries from procmail.log:
In one window, run it without the -d and with the -D. That'll run it in
debug mode in the foreground. In another window, run something through
spamc and see what happens.
> sudden. I have spamd 2.20 installed on 6 servers and, although I
> think they're disregarding /etc/mail/spamassassin/local.cf, they're
> filtering messages and -- most importantly -- they stay running.
2.20 (and later) don't have any problems with the local.cf file, so it
must be something in your configuration. Did any of those directories
exist?
--
Randomly Generated Tagline:
P.S. Perl's master plan (or what passes for one) is to take over the
world like English did. Er, *as* English did...
-- Larry Wall in <[EMAIL PROTECTED]>
-------------------------------------------------------
Sponsored by:
ThinkGeek at http://www.ThinkGeek.com/
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
