chowse at charter.net
Sun Mar 29 13:26:05 PDT 2009
On Mar 29, 2009, at 1:54 PM, Glen Barber wrote:
> On Sun, Mar 29, 2009 at 1:33 PM, Charles Howse <chowse at charter.net>
>> On Mar 28, 2009, at 11:51 PM, Olivier Nicole wrote:
>>>> Webalizer is doing what it's supposed to with httpd-access.log, but
>>>> when I give it the error log to process is coughs, spits and spills
>>>> out errors with no data processed. My research hasn't turned up a
>>>> good solution for webalizer and -error.log.
> What are the errors?
Intrusion attempts, (a few) bad links in my website, also I use the
error.log to troubleshoot cgi scripts.
>>> The format of error log is pretty much different from the format of
>>> transfer log. No wonder webalizer is not liking it. You may have to
>>> write your own format for th error log.
>> Well, can anyone suggest a port that will parse the error.log and
>> output it
>> to a web page that's easy to read?
> Webalizer is probably your best bet.
>> Also, in httpd.conf what level of detail should I set in the
>> error.log to
>> get the most information. It's currently set to 'warn', which I
>> to be 'warn' and everything more critical than that. I don't care
>> about the
>> size of the log, or the amount of garbage per line.
> The 'debug' log level will provide the most verbosity.
More information about the freebsd-questions