On Thu, 1 Jul 1999, James H. Thompson wrote:
> Analog is working fine except that I'm getting periodic
> corrupt logfile lines. Example: on a log file of about 700K lines I get:
>
> Corrupt logfile lines: 708
>
> I tracked it to a line that appears in the logfile of:
>
> 170.38.99.105 - - [30/Jun/1999:00:26:21 -0700] "-" 408 - www.off-road.com
> "-" "-" "-"
>
> >From the HTTP 1.1 RFC: an "408" status code is a Request Time-out
>
> I'm using:
> ApachedefaultLogFormat (%h %l %{junk}i %t \"%r\" %s %b %v \"%{Referer}i\"
> \"%{User-agent}i\" \"%u\")
>
> Line doen't seem corrupt?
>
I agree this isn't really corrupt. I just haven't put in this special case.
Probably I should.
> It would be nice to have an analog option to direct corrupt log file lines
> to a file for later analysis.
>
If you turn debugging on you will get this.
--
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]/
------------------------------------------------------------------------
