Re: [analog-help] Corrupt Log File Entries and MS-Proxy logfiles

1999-02-18 Thread Stephen Turner
No, for speed reasons it never looks ahead, so it ends them at the first comma. -- 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) -

Re: [analog-help] Corrupt Log File Entries and MS-Proxy logfiles

1999-02-18 Thread Wallace Nicoll
Stephen Turner wrote: > 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 th

Re: [analog-help] Corrupt Log File Entries and MS-Proxy logfiles

1999-02-18 Thread Stephen Turner
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 >

[analog-help] Corrupt Log File Entries and MS-Proxy logfiles

1999-02-18 Thread Wallace Nicoll
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 (ru