"W Luke" <[EMAIL PROTECTED]> wrote: > ....not this one. If I use the following LOGFORMAT, it processes this log > file format, but doesn't autodetect the one above (NCSA): > > LOGFORMAT (%m/%d/%Y > %h:%n:%j\t%s\t%v\t%j\t%u\t%j\t%r\t%f\t%j\t%B\t%c\t%b\t%T)
You can specify 2 logformats. Add LOGFORMAT COMBINED as well. > How can I tell it to try the LOGFORMAT as pasted above, but also to > auto-detect the others that don't match it? > > > I doubt that you can write a LOGFORMAT that will allow Analog to > > reliably handle that line, because you have no reliable delimiters > > between fields. For instance, the "and" after "Administrative" is > > supposed to be part of your query, but there's no way that Analog > > can tell that it's not just the next field (which would be the > > browser). > > Damn, that's a problem. I could fix it now easily, by making all URLs > properly URL formatted with %20 where spaces should be. But for the > rest of the log files it'll have to ignore them I see the logformat string you posted uses \t, indicating that the logfile is tab delimited. If that's the case, then you're alright - \t won't match the spaces in the query field. Of course, if your new NCSA combined logs have spaces in the query fields, then your new logs will have broken entries, even if your old ones work. Aengus +------------------------------------------------------------------------ | 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 +------------------------------------------------------------------------
