hi all,
i'm seeing a lot of these messages in my error log:
(32)Broken pipe: core_output_filter: writing data to the network
sometimes it appears by itself, other times, it is paired with this
message:
(104)Connection reset by peer: core_output_filter: writing data to
the network
what doe
yup... i think this is exactly what i'm looking for!
Thanks!
dave
On Oct 30, 2006, at 3:07 PM, Perrin Harkins wrote:
On Mon, 2006-10-30 at 15:02 -0800, Dave Viner wrote:
Sorry for not being clear. Let me try again.
Actually, it's my mistake. I thought you were talking abo
30 at 14:18 -0800, Dave Viner wrote:
from reading the docs on RLimitCPU, http://httpd.apache.org/docs/2.0/
mod/core.html#rlimitcpu , it looks like this applies only to procs
that are _forked_ from apache, rather than the apache children.
I'm not following this. What's the distinctio
from reading the docs on RLimitCPU, http://httpd.apache.org/docs/2.0/
mod/core.html#rlimitcpu , it looks like this applies only to procs
that are _forked_ from apache, rather than the apache children. in
the case of modperl, the child proc is the service-er of the
request is there a con
ile (maybe allocate a buffer, read
in file to buffer, send buffer, repeat until file is eof()... or
something similar). But I've looked in the source, but I can't seem
to convince myself that this will actually happen.
Thanks
dave viner
Hi,
I'm trying to set a special Perl handler for the "homepage" or index
page of a site. A directive like:
SetHandler perl-script
PerlResponseHandler Cool::Handler
causes all requests to be served by Cool::Handler. However, I want
only requests t
guess that's good. apache was just chastising me for
being an idiot. :D
dave
On Sep 14, 2006, at 9:52 AM, Perrin Harkins wrote:
On Wed, 2006-09-13 at 22:05 -0700, Dave Viner wrote:
More information about this error may be available
in the server error log.
Did you look in the error
Hi,
I'm trying to write a simple apache module in perl and have apparent
success. When i request the page from my server, I get the proper
HTML output. However, appended to the end of the proper HTML, is a
second HTML document that says:
.. my html ...
200 OK
OK
The server encounte
