Actually, you would gain a tiny bit -- if a spamc call happens at the moment
when spamd is dead and not yet re-listening on the port, then you'll have a
message or two not filtered (depending on load and timing). If spamd re-reads
its config file without stopping listening on the port, then though it might
take a little longer for those messages to get processed which come in during
the reload, at least they will get processed. Now in practice, who gives a crap
if one or two messages don't get filtered. But still, it would be nice to knock
out http://bugzilla.spamassassin.org/show_bug.cgi?id=469
C
Derrick 'dman' Hudson wrote:
DdH> On Mon, Jun 17, 2002 at 01:39:35PM -0500, David Gibbs wrote:
DdH> | Could someone give me a quick "Spamd 101"?
DdH> |
DdH> | Does spamd reload the local.cf file periodicly, or on demand?
DdH>
DdH> When it starts.
DdH>
DdH> | I'd like to be able to change the site wide spamassassin config and reload
DdH> | spamd without having to kill & restart it.
DdH>
DdH> Why? Restarting it isn't so bad, and even if it provided an interface
DdH> for reloading the config, spamd would be useless while it was
DdH> reloading so you wouldn't gain anything by not restarting it.
DdH>
DdH> -D
DdH>
DdH>
----------------------------------------------------------------------------
Bringing you mounds of caffeinated joy
>>> http://thinkgeek.com/sf <<<
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
