Aengus wrote:
>You are missing one critical part of the puzzle - you can have many
>different LOGFILES in the Analog.cfg, and each one can have a different
>format, so the LOGFORMAT directive must act on LOGFILE entries that come
>after them. And if you specify the logfile on the command line, it comes
>before any LOGFORMAT directives, and therefore they don't apply to
>logfiles specified on the command line.
>
Aha! I knew that the LOGFORMAT command needed to come before the LOGFILE
directive but I *didn't* know that supplying a filename on the command
line would cause LOGFORMAT to be ignored.
>
>The DEFAULTLOGFORMAT directive will apply to any logfile that doesn't
>have a specific LOGFORMAT entry specified.
>
Ok. I'll give that a try and ... it worked! Too bad there isn't also a
DEFAULTAPACHELOGFORMAT, but then again it probably really isn't needed?
Thanks for solving this for me! I did read the online docs over and over
but couldn't come up with anything. You really helped me out!
Jc
PS I *love* analog, it does wonders and it's blazingly fast! (I have 1
GB logs and at first I was using my own shell scripts which took over 30
minutes to run a simple analysis compared to 5 with analog for a
complex analysis!) but the documentation is not an easy read. Once you
finally understand analog's configuration options, *then* the docs
become easier to read, but until you are somewhat proficient with
analog's configuration options the docs are no fun to read. *Not* a
complaint, just a comment.
+------------------------------------------------------------------------
| 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/analog-help@lists.isite.net/
| http://lists.isite.net/listgate/analog-help/archives/
| http://www.tallylist.com/archives/index.cfm/mlist.7
+------------------------------------------------------------------------
