On Wed, 2011-08-24 at 11:35 -0500, Michael Cronenworth wrote: > The cron job: > 10 4 * * * root /usr/share/spamassassin/sa-update.cron 2>&1 | tee -a > /var/log/sa-update.log > > The cron job script: > /usr/share/spamassassin/sa-update.cron > Yep: I see exactly the same cron.d script in Fedora 13 and 15. I can't check Fedora 14 because I replaced it with 15 last week.
IIRC I had about one occurrence of the same sa-update failure back when this was first mentioned. Since then its just worked. Might you have either a network configuration or an SA rules repository access controls problem? NOTES ===== 1) If/when you move to F15, be aware that it is using systemd in place of the old system V init & daemon control system. The main ramification is that, although 'service xxx start|stop' will still work OK in scripts, any script that relies on 'service xxx status' will probably fail. Its best to simply rewrite any scripts that use it to use 'systemctl' instead because that is the way ahead. 2) There is also an issue with UDEV rules that execute programs in /usr/bin if you have /usr in a separate partition. This is best fixed by moving /usr back into the root partition. Contact me offlist if you need more detail on that. Martin
