I just tested this with Analog 6.0 and cannot reproduce this as a bug.
Are you sure you aren't adding "-O-" or something to the command line
that would send the output to stdout? Or are you running this through
the form or something else that is setting CGI/Forms mode?
I am using the following config file:
SETTINGS OFF
DEBUG OFF
WARNINGS ON
PROGRESSFREQ 1000000
# ERRFILE somefile
ERRLINELENGTH 78
OUTPUT COMPUTER
OUTFILE Report.dat
Running analog with the command-line ERRFILE still outputs to the file
and does not write the COMPUTER output to stdout:
$ ./analog -G +gbassam.cfg +C"ERRFILE bassam.err"
./analog: analog version 6.0/Win32
./analog: Warning E: Redirecting future
diagnostic messages to bassam.err
(For help on all errors and warnings, see docs/errors.html)
--
Jeremy Wadsack
Seven Simple Machines
[EMAIL PROTECTED] wrote:
I'm a little confused. Since I'm putting the error file as a command
argument, I would expect anything that gets written to stderr would
equally be written to the log file if the ERRFILE was originally
included in the cfg file. However, I'm overriding the default cfg
with my own as "-G +gCustom.cfg" and only including it as a command
parameter. But if I do include ERRFILE in my Custom.cfg file, I don't
get what I see in the stderr output. So for some reason, stderr is
getting certain information (which doesn't look like error, but like
the COMPUTER output generated - which is probably last week's OUTPUT
since the current week has yet to be generated by Analog) whereas the
ERRFILE gets none of it. How is that possible?
Bassam
-------------- Original message --------------
> On Tue, 19 Jul 2005 [EMAIL PROTECTED] wrote:
>
> > Greetings,
> >
> > I have recently combined all my batch script files to work on
numerous sites
> by passing in the correct arguments for each site. However, in
my common config
> file, I have:
> >
> > SETTINGS OFF
> > DEBUG OFF
> > WARNINGS ON
> > PROGRESSFREQ 1000000
> > # ERRFILE somefile
> > ERRLINELENGTH 78
> >
> > But in my batch script, I am passing +C"ERRFILE %ERRFILE%", where
> > %ERRFILE% is correctly being converted to that site's error
file. The
> > problem I'm having is that the script seems to write out the
computer
> > input data file to the DOS window. Is this because I'm
specifying no
&! gt; > error file in the cfg file, even though Warnings is set
to On? I've taken
> > a look at the batch script, and if I remove the ERRFILE
argument and put
> > it back in the CFG file, it no longer writes the input file to
the screen.
> > Any suggestions?
> >
>
> Commands are processed strictly in the order they occur, and the
ERRFILE is
> not used until it is seen. So any errors previous to the
declaration of the
> ERRFILE will go to stderr. Or a later ERRFILE can override it.
>
> For the order in which each config file and the command line are
read, see
> docs/syntax.html.
>
> --
> Stephen Turner, Cambridge, UK
http://homepage.ntlworld.com/adelie/stephen/
> "Low Priced Cambridge Clare College. Big selection at eBay UK!"
> (Ad after Google search for Clare College Cambridge)
+------------------------------------------------------------------------
| TO UNSUBSCRIBE from this list:
| http://lists.meer.net/mailman/listinfo/analog-help
|
| Analog Documentation: http://analog.cx/docs/Readme.html
| List archives: http://www.analog.cx/docs/mailing.html#listarchives
| Usenet version: news://news.gmane.org/gmane.comp.web.analog.general
+------------------------------------------------------------------------
