https://bugzilla.novell.com/show_bug.cgi?id=676667 https://bugzilla.novell.com/show_bug.cgi?id=676667#c0 Summary: sa-update cronjob should allow amavisd restart Classification: openSUSE Product: openSUSE 11.4 Version: RC 2 Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: varkoly@novell.com ReportedBy: suse-beta@cboltz.de QAContact: qa@suse.de Found By: Beta-Customer Blocker: --- /etc/cron.daily/suse.cron-sa-update (the cronjob that runs sa-update) has an option to run sa-compile. However, the usual way in mailserver setups is to use amavis. Amavis directly includes the spamassassin perl code to avoid an external call to spamassassin for every mail. This also means that amavis needs to be restarted after running sa-update to activate the new rules sa-update downloaded. Please add some code to restart amavis to suse.cron-sa-update. BTW: sa-update indicates in the exit code if there were new rules. This means checking the exit code can avoid useless restarts of amavis.

From sa-update(1): An exit code of 0 means an update was available, and was downloaded and installed successfully if --checkonly was not specified.

An exit code of 1 means no fresh updates were available. [...] Therefore I propose to change suse.cron-sa-update like this: (untested, but should work - the code adds the amavis restart and also some error logging in case sa-update fails.) # [...] if [ "$SPAM_SA_UPDATE" = "yes" ] then /usr/bin/sa-update &> /dev/null result=$? if [ "$SPAM_SA_COMPILE" = "yes" -a $result = 0 ] ; then /usr/bin/sa-compile &> /dev/null fi if [ "$SPAM_AMAVISD_RESTART" = "yes" -a $result = 0 ] ; then /etc/init.d/amavis restart &> /dev/null fi if [ $result = 2 ] ; then echo "sa-update lint check failed" | \ logger -t suse.cron-sa-update fi if [ $result -ge 3 ] ; then echo "sa-update failed, exitcode $result" | \ logger -t suse.cron-sa-update fi fi exit 0 You probably have noticed $SPAM_AMAVISD_RESTART in the code above - please add it to /etc/sysconfig/spamd This bug affects all openSUSE releases. Please consider a backport to 11.2 and 11.3 (and 11.4 - I guess it's too late to fix it in the goldmaster). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.