Am 11.09.2015 um 17:54 schrieb RW:
On Fri, 11 Sep 2015 08:21:15 -0700 Ian Zimmerman wrote:On 2015-08-14 17:45 +0200, Reindl Harald wrote:Can I safely upgrade SA from 3.4.0 to 3.4.1 without changing any local configuration files, and without regenerating the Bayes database? (I use the default bdb Bayes store.)yes, but you need to run "sa-update" before restart to fetch the latest rules and hopefully have a distribution which restarts automatically after update the packageIsn't this a contradiction? If my distribution automatically restarts (which it does), how can I sneak in a sa-update run after the upgrade but before the restart?You need a restart to run the new software or pickup new rules. You don't need to avoid a restart between a package update and a rule update.
i saw spamassassin just crash after upgrade on Fedora before /var/lib/spamassassin/3.004001/ was filled by sa-update and i remember at least one post on this list observing the same problem on a different environment
If you are running sa-update from cron you don't really need to run it manually unless you are updating from a very old version that didn't support sa-update or no longer receives updates
you are aware that the previous version don't matter 3.4.1 uses /var/lib/spamassassin/3.004001/ 3.4.0 uses /var/lib/spamassassin/3.004000/ so it is *completly* irrelevant from which version you upgrade
signature.asc
Description: OpenPGP digital signature
