On Thu, 2014-10-09 at 18:08 +0700, Olivier Nicole wrote: > But you don't do a -lint before restarting SA: if an update was to break > SA (like a big Perl syntax error in a rule, or you are working on a > plugin on your production system, you feel safe because as long as you > don't restart spamd, any bad modification you make will not break SA), > you have stoppped the one that is currently working (and that could keep > working despite the update) amd you find yourself trying to restart a > broken version of SA. > This isn't my production system: that is updated daily by the standard RedHat cron job. This copy of SA is only run when I'm writing/modifying rules or (much less often) working in a plugin. It is stopped 99% of the time. It goes without saying that I use -lint during rule or plugin development.
I'm certain that there is a lot in this script you could criticise, but it does exactly what I need: pulls down any updated rules on a weekly basis and finds any obvious errors in the download by starting and stopping spamd and reporting its operation via logwatch. I posted it to show anybody who doesn't use bash case statements just how readable they can make a shell script. Martin
