On Thu, 18 Feb 1999, Wallace Nicoll wrote:
> In an earlier posting to the list I asked if anyone had run analog against MSproxy
> logs thinking that there was something in the log formats that was causing a huge
> number of corrupt lines. It now turns out it was the result of embedded commas in
> the URL. By changing these to another character (runnning the log files through a
> sed script under UNIX) I can analog the logfiles and only get a handful of corrupt
> lines each day (20Mb logfiles).
>
> Am I right in thinking that this could cause the problem?
Are the fields normally separated with commas? If so, that is exactly the
problem. Analog doesn't know where the field stops.
There's another thread on this subject going on right at the minute, called
Corrupt Log File Entries. Have a look at that for more discussion. (If you
missed the postings, they're archived at www.mail-archive.com).
--
Stephen Turner [EMAIL PROTECTED] http://www.statslab.cam.ac.uk/~sret1/
Statistical Laboratory, 16 Mill Lane, Cambridge CB2 1SB, England
"Ad infinitum, if not ad nauseam." (Interviewee, BBC Radio 4)
--------------------------------------------------------------------
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.
--------------------------------------------------------------------
