Yes I did put LOGFORMAT before LOGFILE. Though I run analog from the
command line like this:
#analog ./access.log
So I would think that the cfg file's LOGFILE directive is ignored?
Also am I right in thinking that the order of the various LOGFORMAT
directives is unimportant?
I'm still confused as to why analog refuses to parse this log file in
it's entirety but will happily parse the lines if spurts out as being
"invalid". Is analog getting confused because of the multiple formats
used in the file? (From reading the documentation though it seems analog
just tries all the formats it already knows and then all the ones in the
cfg file for *each* line, so I can't see why it gets confused).
If however it's something *I* did wrong (error in the log file, in the
config file) please let me know.
Jc
Here are the first line from my cfg file (I'm using analog 5.24 and a
cfg file made for 5.23):
# Configuration file for analog 5.23
DEBUG C
APACHELOGFORMAT (%h %l %u %t \"%r\" %>s %b \"REF: %{Referer}i\"
\"%{User-Agent}i\")
APACHELOGFORMAT (%h %l %u %t \"%r\" %>s %b \"%{Referer}i\"
\"%{User-Agent}i\")
LOGFORMAT COMMON
LOGFORMAT COMBINED
LOGFILE access.log
Stephen Turner wrote:
>On Thu, 27 Jun 2002, Jean-Christian Imbeault wrote:
>
>>Sorry to bug the list again but does anyone have any suggestions on how
>>I can analog to parse my log file even though it contains lines with
>>varying logging formats?
>>
>
>You did put the LOGFORMAT commands above the LOGFILE command, did you?
>
+------------------------------------------------------------------------
| 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
+------------------------------------------------------------------------
