Hello,
I have a script which calls analog numerous times to process different sets of log
files. I have been using this script as a cron job successfully for years now
(updating it everytime I upgrade analog -- I'm currently using 3.0), without any
problems on my Slackware Linux machine. I recently attempted to use this script on my
RedHat 5 Linux machines, and it worked as expected. That is, until I ran it in cron.
When running the script in cron, analog does not successfully decompress my compressed
log files. I have tried many remedies, including (but not limited to) explicitly
nameing the path to zcat in my 'UNCOMPRESS' directive, explicitly exporting the PATH
environment variable in my front-end script, and calling analog directly from a cron
entry. ALL of these yield the same results -- analog executes, processes the
uncompressed log files, and returns errors regarding all the compressed log files :
-----
/usr/sbin/analog: Warning F: Problems uncompressing logfile
/var/www/logs/access_log.0.gz
(For help on all errors and warnings, see docs/errors.html)
/usr/sbin/analog: Warning F: Problems uncompressing logfile
/var/www/logs/access_log.1.gz
/usr/sbin/analog: Warning F: Problems uncompressing logfile
/var/www/logs/access_log.2.gz
-----
The strangest thing of all is that the data looks correct. I can't verify this for
sure, but it may work anyway.
Any idea why this might be occurring?
Thanks,
David Pisoni -- <[EMAIL PROTECTED]>
CyberNation -- <http://www.cnation.com/>
310/689-3170 -- 310/689-3174 (fax)
"If God lived on Earth, people would knock out all His windows."
-- Yiddish saying
--------------------------------------------------------------------
This is the analog-help mailing list. To unsubscribe from this
mailing list, send mail to [EMAIL PROTECTED]
with "unsubscribe analog-help" in the main BODY OF THE MESSAGE.
--------------------------------------------------------------------
