On Tue, 21 Sep 1999, ikong wrote:
> >
> > Maybe there's a LOGFORMAT command in analog.cfg which is telling analog the
> > log format when the LOGFILE command is in analog.cfg too, but analog doesn't
> > know the format when the logfile is specified on the command line.
> >
> > Perhaps I should be more explicit. All commands work on the command line.
> > But if you move a command out of a configuration file onto the command line,
> > you won't necessarily get exactly the same report because the order of
> > commands can be important too.
>
> What are the reasons for having the order be important? I have
> discovered that by accident before, and it can be quite confusing.
>
For most commands it doesn't matter. But sometimes it can. For example:
(1) If you have both an INCLUDE and an EXCLUDE of the same type, then the
order matters: including a but excluding b is quite different from
excluding b but including a.
(2) LOGFORMATs only apply to LOGFILEs later in the same configuration
file. (It would be much more confusing if they could spread further.
If you need them to spread further, use DEFAULTLOGFORMAT).
--
Stephen Turner [EMAIL PROTECTED] http://www.statslab.cam.ac.uk/~sret1/
Statistical Laboratory, 16 Mill Lane, Cambridge CB2 1SB, England
"Due to the conflict in Kosovo, we will not be showing the movie Wag the
Dog. Instead, we will show Mortal Kombat: Annihilation." Cable & Wireless
------------------------------------------------------------------------
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.
List archived at http://www.mail-archive.com/[email protected]/
------------------------------------------------------------------------
