> On Feb 4, 2015, at 8:34 PM, David B Funk <dbf...@engineering.uiowa.edu> wrote: > > On Wed, 4 Feb 2015, LuKreme wrote: > >> On Feb 4, 2015, at 8:57 AM, Joe Quinn <jqu...@pccc.com> wrote: >>> Perhaps /usr/local/bin is not on PATH for the cron user? >> >> I don’t understand what you are saying. The crontab lists the full path. >> >>>> # crontab -l |grep sa-update >>>> 16 1 * * * /usr/local/bin/sa-update && /usr/local/bin/sa-compile && >>>> /usr/local/etc/rc.d/sa-spamd restart > > You are right but the things -inside- that "sa-update" script do not have the > full path for each of their tools they use. Thus the "gpg" utility must > be in a directory included in the $PATH variable that the script inherits.
Ah, right. The script returns PATH=/usr/bin:/bin Seems the sa-update script should be able to figure out the location for gpg. Now what? -- A good friend will come and bail you out of jail but a true friend will be sitting next to you saying, "Dang, that was fun."
