You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@spamassassin.apache.org by bu...@bugzilla.spamassassin.org on 2005/03/21 01:02:48 UTC

[Bug 4210] New: spamd should check periodically for updated rule files and reload SA

http://bugzilla.spamassassin.org/show_bug.cgi?id=4210

           Summary: spamd should check periodically for updated rule files
                    and reload SA
           Product: Spamassassin
           Version: SVN Trunk (Latest Devel Version)
          Platform: Other
        OS/Version: other
            Status: NEW
          Severity: enhancement
          Priority: P3
         Component: spamc/spamd
        AssignedTo: dev@spamassassin.apache.org
        ReportedBy: lwilton@earthlink.net


This request greq out of the periodic discussion on the SA talk list about the 
need to restart spamd after updating rules.

It is suggested that spamd check at fairly rare intervals for updated rules 
files and if found, do whatever is necessary to get the rules files reloaded.

Since children now live for fairly long intervals (usually), it might be 
reasonable to check when restarting a child that gave up.  Alternately, every 
half hour, or evenr N mail transactions or some such.

In all probability the bare check for updated rules files is less painful than 
scanning a single mail message with net tests enabled.  So, on that assumption, 
checking every 100 mail messages would only add about 1% to the system load, 
which is probably acceptable on almost all systems.  Clearly a reload of the 
rules is more painful than this; but it is only done when it needs to be.

While there could be all kinds of user options to deal with this concept, I 
suspect that an internal rule that says to check no more often than every 5 
minutes nor less often than every half hour would be sufficient.

BTW, to increase robustness, spamd could farm off a --lint check before 
adopting any new rules that are discovered, and only adopt the rules if the 
lint check passes.  This doubles the overhead for grabbing new rules files, but 
the safety would proabbly be worth it.



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

[Bug 4210] spamd should check periodically for updated rule files and reload SA

Posted by bu...@bugzilla.spamassassin.org.
http://bugzilla.spamassassin.org/show_bug.cgi?id=4210





------- Additional Comments From felicity@kluge.net  2005-03-20 16:15 -------
Subject: Re:   New: spamd should check periodically for updated rule files and reload SA

On Sun, Mar 20, 2005 at 04:02:48PM -0800, bugzilla-daemon@bugzilla.spamassassin.org wrote:
> It is suggested that spamd check at fairly rare intervals for updated rules 
> files and if found, do whatever is necessary to get the rules files reloaded.

I'm -1 on this idea.

First, I can't think of any other daemon that does this.

Second, there are situations where the rule file(s) may be modified but the
daemon should not be restarted.  For instance, if I was prepping some new
whitelist entries, but wanted to wait until after business hours ...

Third, it's inefficient.  Just HUP spamd when the config files are changed.
The admin knows when they are doing something to change the config.

Fourth, as you brought up, there may be changes which cause errors, and an
auto-restart may make the daemon die unexpectedly.





------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

[Bug 4210] spamd should check periodically for updated rule files and reload SA

Posted by bu...@bugzilla.spamassassin.org.
http://bugzilla.spamassassin.org/show_bug.cgi?id=4210


spamassassin-contrib@msquadrat.de changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |DUPLICATE




------- Additional Comments From spamassassin-contrib@msquadrat.de  2005-03-22 14:40 -------


*** This bug has been marked as a duplicate of 3033 ***



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.