Re: Effectiveness

[Matt]

This server connects to the Internet through an AT&T managed Cisco 3640 so 
the network should be up instantly.  Although it runs as its own DNS server. 
Perhaps named is not fully up when SPMAD starts?

Is there something like "cron.fiveminutesafterbootup" that I can do a spamd 
restart in?

Matt
Ahmmm, when is the network coming up vis a vis the time spamassassin
comes up? This is a problem I have marked for myself when the 3.0.2
machine goes up as the firewall/caching DNS machine as well. I suspect
that spamd coming up before the main network comes up is a problem. And
I discovered that a DSL connection coming up during the boot cycle before
any consoles could be used could leave the machine locked and unusable
if the DSL modem or phone lines had a severe headcold while I was booting.
So I bring the DSL up very late in the boot cycle. I suspect I'll have
to put a line "service spamassassin restart" right after I start the
DSL. But more likely I'd just have to make sure DNS caching is up before
I bring up spamassassin. And I think that's the normal order.
This is weird.  I have "chkconfig spamassassin on" now.  I reboot the
router.  SPAMD is running when it comes back up but I am not getting any
URIBL tags in headers of SPAM messages even the test messages I send
through
that are supposed to trigger it.  I do a "spamassassin restart" then it
all
works.
Whats the deal, any ideas?  For now I have added a spamd restart to
cron.daily just in case.