Paul
Aengus wrote:
Paul Shackleton <[EMAIL PROTECTED]> wrote:Dear Colleagues,I have been using analog successfully for some time but I have been forced to run the script manually due to a failure of the script to run correctly from the cron. Platform is Solaris 8, cron line : 45 6 * * 0 /bin/su - root -c "/usr/local/analog/analog-5.24/analog" >/scratch/analog.rep 2>&1 The script runs and the logs are read but the FROM and TO directives seem to be ignored and an empty report is produced. But if I simply run the command line ./analog manually on the Monday, without changing the config file, it produces the report for the period specified. I have used relative and fixed dates for the FROM and TO directives but the problem persists. The script is scheduled to run on Sunday morning and appears to only look for log file activity from the Apache restart that takes place at 6am, that is 45 minutes earlier. I am probably missing something really obvious so apologies in advance - I have read the manual on this one!The usual problem with running Analog under cron is permissions - the cron task doesn't have permission to access the same files that you do when you run at the command line. What makes you think that the logs are read? If the problem was with the FROM/TO directives, you wouldn't expect an empty report - Analog would include everything. Aengus +------------------------------------------------------------------------ | TO UNSUBSCRIBE from this list: | http://lists.isite.net/listgate/analog-help/unsubscribe.html | | Digest version: http://lists.isite.net/listgate/analog-help-digest/ | Usenet version: news://news.gmane.org/gmane.comp.web.analog.general | List archives: http://www.analog.cx/docs/mailing.html#listarchives +------------------------------------------------------------------------
