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.
Try this; create a test script "/usr/local/bin/sa-path-check"
and in that script put a "which gpg" command and run that as a
cron job and see what output it generates.
(you could also put a "echo $PATH" in the script to see exactly
what the path actuall is for that environment.)
--
Dave Funk University of Iowa
<dbfunk (at) engineering.uiowa.edu> College of Engineering
319/335-5751 FAX: 319/384-0549 1256 Seamans Center
Sys_admin/Postmaster/cell_admin Iowa City, IA 52242-1527
#include <std_disclaimer.h>
Better is not better, 'standard' is better. B{
