Duke Hillard ([EMAIL PROTECTED]):
> 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 You can add any Analog command to the command line with +C: /web/utils/analog/analog +g$cfg +C"ERRFILE /tmp/analogerrors/$cfg" You can also use redirection on the command line to accomplish this (which is why there's no command-line argument for it): /web/utils/analog/analog +g$cfg 2> /tmp/analogerrors/$cfg Finally, if you want to trace the processing, use the PROGRESSFREQ command to get messages every so often during the run. See http://www.analog.cx/docs/debug.html#PROGRESSFREQ for details -- Jeremy Wadsack Wadsack-Allen Digital Group +------------------------------------------------------------------------ | 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 +------------------------------------------------------------------------
