On Thu, 2010-01-07 at 19:14 -0700, clem...@dwf.com wrote:
> How do I tell if sa-update is actually running?
> I mean, yes, I can run it by hand and get no error messages, and with -D
> I dont see any problems, still I feel that my stuff isnt current, and that
> there
> should be an update.
>
> Should I be getting a message in /var/log/messages? or /var/log/maillog?
> or /var/log/sa-update.log ???
>
I run this script as a weekly cron job:
==========================================================================
#!/bin/bash
#
# Update the Spamassassin rules
#
sau=/usr/bin/sa-update
if [ -x $chkd ]
then
$sau
err=$?
case $err in
0) echo "Spamassassin rules update completed.";
service spamassassin restart;
echo "Spamassassin restarted." ;;
1) echo "No Spamassassin rule updates available.";;
2) echo "Spamassassin rules updates available";
echo "Site pre files lint check failed.";
echo "Fix the files and try again.";;
*) echo "Spamassassin rules update failed: error=$err"
esac
else
echo "Error: $sau does not exist"
exit 0
fi
====================================================================
Its not a silent script, so crond mails root the results: Since I
set /etc/aliases to redirect mail to root to my usual login, I'll see
what sa_update did the next day.
Martin
