Thanks, Matt. I call my sa-update in a script from cron. I don't think I have a permissions problem, but I agree, that is what it looks like. Perhaps this will shed a little light.
skipmor...@ps11651:~$ id uid=15203(skipmorrow) gid=588771(pg2222652) groups=588771(pg2222652) skipmor...@ps11651:~$ whoami skipmorrow skipmor...@ps11651:~$ crontab -l ###--- BEGIN DREAMHOST BLOCK ###--- Changes made to this part of the file WILL be destroyed! # sa-update JM_SOUGHT MAILTO="s...@pelorus.org" @hourly /usr/local/bin/setlock -n /tmp/cronlock.4061564.53932 sh -c $'/home/skipmorrow/update_sa_rules.sh' ###--- You can make changes below the next line and they will be preserved! ###--- END DREAMHOST BLOCK skipmor...@ps11651:~$ tail sa_update.log Mon Jul 20 07:00:04 PDT 2009 Who Am I: skipmorrow id: uid=15203(skipmorrow) gid=588771(pg2222652) groups=588771(pg2222652) skipmor...@ps11651:~$ cat update_sa_rules.sh #!/bin/bash echo `date`>>/home/skipmorrow/sa_update.log echo "Who Am I: `whoami`">>/home/skipmorrow/sa_update.log echo "id: `id`">>/home/skipmorrow/sa_update.log echo "">>/home/skipmorrow/sa_update.log /home/skipmorrow/bin/sa-update -D --gpgkey 6C6191E3 --channel sought.rules.yerp.org --gpghomedir /home/skipmorrow/etc/mail/spamassassin/sa-update-keys I just recently added the gpghomedir, but that didn't make a difference at all to the error messages, and I wouldn't have expected it to make a difference, since sa-update is finding that directory on its own anyway. I would be most appreciative of any other ideas that you may have. Skip -- View this message in context: http://www.nabble.com/sa-update-errors-tp24569115p24570739.html Sent from the SpamAssassin - Users mailing list archive at Nabble.com.
