On Fri, Oct 29, 2010 at 03:39:14PM -0300, Santiago Liz wrote:
> Running /etc/cron.daily/spamassassin this download updates but does not
> compile and do not reload spamassassin.
> Because not match the default directory of sa-update and directory searched
> for the script.
>
> ....
> sa-update:
> --updatedir path Directory to place updates, defaults to the
> SpamAssassin site rules directory
> (default: /var/lib/spamassassin/3.003001) <----
> the directory does not match
> sa-compile:
> --updatedir=path Directory to place updates
> (default:
> /var/lib/spamassassin/compiled/<perlversion>/3.003001)
> ....
>
> do_compile() {
> # Compile, if rules have previously been compiled, and it's possible
> if [ -x /usr/bin/re2c -a -x /usr/bin/sa-compile \
> -a -d /var/lib/spamassassin/compiled ]; then <----
> the directory does not match
> sa-compile --quiet
> # Fixup perms -- group and other should be able to
> # read and execute, but never write. Works around
> # sa-compile's failure to obey umask.
> if [ -d /var/lib/spamassassin ]; then
> chmod -R go-w,go+rX /var/lib/spamassassin/
> fi
> fi
> }
>
> ....
>
> This run to my:
>
> diff /etc/cron.daily/spamassassin /etc/cron.daily/spamassassin.local
> a64c64
> < sa-update
> ---
> > sa-update --updatedir=/var/lib/spamassassin/compiledNo, the script is functioning as designed. You shouldn't be putting your spamassassin rule updates in /var/lib/spamassassin/compiled If you manually run sa-compile, /var/lib/spamassassin/compiled will be created, and then the test will pass in future runs of the do_compile function. The idea is that unless you've manually run sa-compile, it is assumed that you don't want to run it via the cron script. This may change in squeeze+1, since there's a patch available to split sa-compile into a separate package. At that point, the assumption will be that if you have sa-compile installed, you want to use it. noah
signature.asc
Description: Digital signature
