On Tuesday, July 31, 2007 7:33 AM [EDT], Aimee Mandeville <[EMAIL PROTECTED]> wrote:
Thanks for the clarification on that. Do you have any thoughts as to why Analog is having difficulty parsing these lines? I've attached a sample of the CORRUPT lines. The log file I am analyzing has 69,989 lines and 65,634 of them are corrupt. I am using the following format: LOGFORMAT (#%j) LOGFORMAT (%S\t%u\t%B\t%Y-%m-%d\t%h:%n:%j\t%j\t%j\t%j\t%j\t%j\t%j\t%j\t%b\t%j\t%j\ t%r\t%j\t%c\twww.usawaterquality.org\t%j)
You haven't provided any examples of the lines that Analog considers corrupt, but at a guess, they don't have www.usawaterquality.org in them.
If you enable debugging (DEBUG ON), Analog will generate output that will indicate where the line stops matching th LOGFORMAT Analog expected to find.
Aengus +------------------------------------------------------------------------ | TO UNSUBSCRIBE from this list: | http://lists.meer.net/mailman/listinfo/analog-help | | Analog Documentation: http://analog.cx/docs/Readme.html | List archives: http://www.analog.cx/docs/mailing.html#listarchives | Usenet version: news://news.gmane.org/gmane.comp.web.analog.general +------------------------------------------------------------------------
