On 22 Oct 2005, 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.
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?
--
Mark Nipper e-contacts:
832 Tanglewood Drive [EMAIL PROTECTED]
Bryan, Texas 77802-4013 http://nipsy.bitgnome.net/
(979)575-3193 AIM/Yahoo: texasnipsy ICQ: 66971617
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GG/IT d- s++:+ a- C++$ UBL++++$ P--->+++ L+++$ !E---
W++(--) N+ o K++ w(---) O++ M V(--) PS+++(+) PE(--)
Y+ PGP t+ 5 X R tv b+++@ DI+(++) D+ G e h r++ y+(**)
------END GEEK CODE BLOCK------
---begin random quote of the moment---
"It is better to sit in silence and appear ignorant, than
to open your mouth and remove all doubt."
-- Mark Twain
----end random quote of the moment----
_______________________________________________
Cherokee mailing list
[email protected]
http://www.alobbs.com/cgi-bin/mailman/listinfo/cherokee
