At 03:15 PM 10/8/01 -0500, Cameron Moore wrote: >I'm seeing the exact same problem (same version of webalizer but newer >apache). Nothing was changed on the box -- it just stopped working. >Plenty of resources (disk, memory, etc). Seems like a webalizer bug. >First one to figure out the problem speak up. :-)
Back up all the webalizer.* files, then cut the log file up into pieces and figure out which one is giving webalizer such a headache? If there's a particular malformed line involved, Perl might be able to make the logchunk more palatable for it. -- Asher Densmore-Lynn <[EMAIL PROTECTED]>
