Mark Nipper wrote:
>> So my guess would be either whatever path is being exercised by
>> that 206 response from the rather abusive client at 202.155.126.36
>> or something in the logging path.
These connections don't look bad to me.. it is only a guy who is
using a download accelerator, it should be ok. :-m
> Crap, I don't know. I just disabled logging by commenting out:
> ---
> #Log combined {
> # AccessLog /var/log/cherokee.access
> # ErrorLog /var/log/cherokee.error
> #}
>
> I'm not sure that actually disabled the logging code path, but
> the server is wedged again.
>
> Does that actually disable the logging code path?
Yeah, with that configuration it won't even create a logger object
in memory.
I'm working in this problem right now, I will let you know as soon
as I get something. Meanwhile, if you discover something new, please
drop me a line ':)
--
Greetings, alo.
http://www.alobbs.com
_______________________________________________
Cherokee mailing list
[email protected]
http://www.alobbs.com/cgi-bin/mailman/listinfo/cherokee
