Good thinking...I think I found the problem. qtp-sa-update is in
cron.daily, and by the looks of it, this script restarts SA after
updating the rules. Sometimes we just overlook the obvious, huh?
Thanks!
Casey Price
Smile Global Technical Support
Submit or check trouble tickets http://billing.smileglobal.com
www.smileglobal.com <http://www.smileglobal.com>
Follow us on Twitter <https://twitter.com/#%21/SmileInternet>
Like us on Facebook <https://www.facebook.com/smileglobal>
On 12/1/11 9:12 AM, Eric Shubert wrote:
On 11/30/2011 09:22 PM, Casey Price wrote:
Ok, maybe I'm missing something here, but I can't seem to keep spamd and
spamd/log from restarting. Since we have our gateway servers separate
from our spamassassin boxes, we don't usually run spamd on them since
they are running spamdyke.
I updated some QMT packages about a week or two ago, and it seems like
ever since, spamd wants to run all the time.
I tried a few different things: qmail-spam stop, and then I cd'd into
/var/qmail/supervise and did a 'touch spamd/down' and 'touch
spamd/log/down'. Everything works as it should, but then if I log into
the server the next day, spamd & spamd/log will be running again, and a
quick qmailctl stat will show "spamd up xxx seconds, normally down", and
something to the same effect for spamd/log.
What am I missing here? Running CentOS 5.7
--
Or perhaps a cron job that's starting it as part of some other daily
maintenance?
