Thanks for the tip, Stephen. In spite of using analog for awhile,
it's difficult, at times, to keep track of its many features (in spite
of excellent documentation).
In my original message, I mentioned that I had experienced lag
times of an hour or less in the past. So, I was surprised when
the lag time jumped up to 7 hours after upgrading to 5.22. But,
I don't know that the increase is related to analog. I had hoped
that using the ERRFILE command would help me track analog's
progress, but the ERRFILE is overwritten every time I run analog.
I didn't see a command line equivalent of ERRFILE in the manual.
A command line equivalent could help analog users who have a
large number of runs or config files by allowing a command line
argument like the following example in Unix
for cfg in /web/utils/analog/cfg/*; do
/web/utils/analog/analog +g$cfg +ERR/tmp/analogerrors/$cfg
done
Thank you for considering the idea. And thank you for analog.
-- Duke Hillard
Stephen Turner wrote:
>On Tue, 2 Apr 2002, Duke Hillard wrote:
>
>>Why is there a difference of almost 7 hours from the time of my
>>last log entry and the end of the 7-day period? How does Analog
>>establish the 7-day period?
>>
>
>See docs/defns.html or docs/reports.html
>
+------------------------------------------------------------------------
| This is the analog-help mailing list. To unsubscribe from this
| mailing list, go to
| http://lists.isite.net/listgate/analog-help/unsubscribe.html
|
| List archives are available at
| http://www.mail-archive.com/[email protected]/
| http://lists.isite.net/listgate/analog-help/archives/
| http://www.tallylist.com/archives/index.cfm/mlist.7
+------------------------------------------------------------------------
