In article
<[EMAIL PROTECTED]>,
Stephen Turner <[EMAIL PROTECTED]> wrote:
> Well, my guess is that you just need to write a LOGFORMAT command to
> tell analog the format of your logfile. See docs/logfmt.html for
> instructions. If you have trouble, send the top 10 lines of your logfile
> here, and someone will help you with it.
In article <[EMAIL PROTECTED]>, Aengus Lawlor
<[EMAIL PROTECTED]> wrote:
> If the first two months are okay, it sounds like the ISP may have
> changed logformats at some point. Analog can cope with more than one log
> format in a single file, but you may have to add multiple LOGFIRMAT
> commands to the config file.
> Add DEBUG C to your analog.cfg to display the "corrupt" entries, and
> post an example of a corrupt line, as well as a line that works from the
> beginning of the log.
Thanks both for your help. I used a screenshot of the DOS window with
DEBUG C on to get the format of the "corrupt lines" and correctly guessed
that LOGFORMAT COMMON would take care of the earlier lines.
I wish I could work out a way to look at lines of large files in Windows
as that would have made it a lot easier. This size file seems to lock up
Wordpad or Notepad.
Thanks again
------------------------------------------------------------------------
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/analog-help@lists.isite.net/
------------------------------------------------------------------------
