Stephen Turner wrote:
> On Tue, 9 Mar 1999, Jeremy Wadsack wrote:
> >
> > Related Question for Stephen: Since we run analog as a scheduled task it
> > runs when no one's around to watch the output, but I'd like to log the
> > analog output. I've tried just redircting (e.g. anaolog >analog.log) but
> > the Win32 binary version doesn't seem to write to STDOUT, so nothing gets
> > to the logs. Is this a compile/platform thing, a code thing or is there
> > another way log the output from analog?
> >
>
> It sends it somewhere -- wherever your OUTFILE is set to.
>
> OUTFILE stdout (or OUTFILE - ) will send it to standard output, by the way.
>
Hmm... Maybe we've different definitions of 'analog output'. What I want in for
analog to create the report file as it normally does (which is what the OUTFILE
command is for), but when I run it it sends all warnings and errors to the
screen. These are what I'm trying to capture to a log file for later perusal. I
would expect to beable to run a command like
analog > analog.log
And have analog read and interpret analog.cfg, read logs specified in LOGFILE,
write a report to the file specified in OUTFILE and have any warning messages
and error appear in analog.log.
I hope that is clearer. Is there a way to do this?
Thanks,
Jeremy Wadsack
OutQuest Magazine
a Wadsack-Allen publication
--------------------------------------------------------------------
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.
--------------------------------------------------------------------
