Daryl C. W. O'Shea wrote:
I overlooked a couple ways that you could legitimately break a --lint
between updates, nobody else caught it either, so sa-update was (the
only thing) broken for some people in the SA 3.1.6 release. SA 3.1.7
reverted to the simpler --lint check of the update itself only.
Heh? How do I check just the update rules? Your statment implies
that's what it does... (note I'm running 3.1.5 at the moment)
For now, running an sa-update, then a spamassassin --lint, and then
restarting is pretty safe though.
sa-update [whatever] && spamassassin --lint && whatever-to-restart
I've been having some issues with the restarts, and when that happens
mail is down.
I'm kindof hoping that there will be some way to get SA to re-read the
rules *WITHOUT* restarting the process.
Milters tend to get confused/upset when the daemon talking to it goes
away, likewise with amavis getting upset when SA goes away suddenly, etc.
> 3.2.0 will include an improved lint process. Pending enough testing
> (and me/somebody getting around to writing the code) it might show up
> sooner.
I'd rather enable some sort of inline reconfig of the SA rulset...
--
Jo Rhett
Network/Software Engineer
Net Consonance
