Hi Guys/Gals,
Thanks to the following folks:
"Sheila Hollenbaugh" <shollen_at_cs.wright.edu>
"Skeate, Scott B" <scott.b.skeate_at_lmco.com>
"Sean O'Connell" <sean_at_stat.Duke.EDU>
alan_at_nabeth.cxo.dec.com
"Dr. Tom Blinn" <tpb_at_doctor.zk3.dec.com>
"Bruce B. Platt" <bbp_at_comport.com>
Bruce Hines <Bruce.Hines_at_mci.com>
"Kevin Oberman" <oberman_at_es.net>
Rich Lafferty <rich_at_alcor.concordia.ca>
"Nestor Ruiz" <nruiz_at_hermes.bvl.com.pe>
As ever Dr. Tom Blinn rides again, together with Nestor
Ruiz. They provided the solution that works to me, namely
just add a symbolic link for gzip in /usr/bin pointing to
/usr/local/bin/gzip.
Some people also suggested to give the full path whenever
gzip is called inside aw-parser but I preferred not to
edit that copyrighted file.
Sean O'Connell suggested to include the PATH command in
my script but unfortunately it did not work in this case.
Below are the original post and the instructive message
from Dr. Tom Blinn.
Oyanarte Portilho
Institute of Physics
University of Brasilia, Brazil
---------
(original)
Hi Gurus,
I have edited crontab in order to run periodically a script
containing two commands related to Accesswatch data update:
aw-parser and aw-report. The data are collected from the
access_log file generated by httpd. However cron complains
not finding gzip as can be noticed from its e-mail to root:
sh: gzip: not found
However if I run the script manually everything works fine.
How can I teach cron to find gzip's path, i.e., /usr/local/bin?
--------
--------
(Dr. Tom Blinn' reply):
With great diffculty. Cron is NOT a shell. It gets run from init, which is
not a shell. You can either put a symlink to gzip in the usual places where
the default root path would find it (e.g., in /usr/bin), or you can edit
your shell script to add /usr/local/bin to the PATH before you attempt to
run the section that runs gzip.
Received on Thu Oct 15 1998 - 21:09:06 NZDT