Brad K. ([EMAIL PROTECTED]): > Just joined the list for some support here. Now, I'm not a computer dummy > (am a sysadmin and can program in perl) but I know something is wrong. > Wanting to analyze cacheflow logs. Generated in either Common or Squid > format. No LOGFORMAT string will make analog (or webalizer) happy. Brought > up portion of a log in debug to see what characters were there. Turns out, > that there is an extra carriage return character (0x0d) in the end-of-line > sequence. > Is there any way to force Analog to read the *3* character end of line > sequence as a true EOL? Analog should just interpret the extra characters as a new line and ignore it. You could try adding this logformat: LOGFORMAT \n > (I'm also trying to write a filter in perl to remove > the extraneous characters but having little luck.) perl -pe's/[\012\015]+/\n/' < logfile > logfile.new -- Jeremy Wadsack Wadsack-Allen Digital Group +------------------------------------------------------------------------ | This is the analog-help mailing list. To unsubscribe from this | mailing list, go to | http://lists.isite.net/listgate/analog-help/unsubscribe.html | | List archives are available at | http://www.mail-archive.com/[email protected]/ | http://lists.isite.net/listgate/analog-help/archives/ | http://www.tallylist.com/archives/index.cfm/mlist.7 +------------------------------------------------------------------------
