Actually, all children seem to segfault now right after the broken pipe,
so it's easier to troubleshoot. I'm using prefork. That'll make it
easier to find.
On Tuesday, April 10, 2001, at 07:50 PM, Graham Leggett wrote:
Chuck Murcko wrote:
[error] (32)Broken pipe: core_output_filter: writing data to the
network
Now that the threading is fixed - I've started getting these.
Interestingly enough I don't see any broken or incomplete images as a
result of this using Netscape v4.7.
Can you check if this error is causing any broken downloads? - it could
theoretically be browser badness, where the browser retries the
connection.
Hmmm - the error is thrown after the body has finished being transmitted
- it could be that the browser is closing the connection before all
bytes are written, which in turn could be because we're writing too much
data...
