From: John P. Looney (jplooney-ilug at domain online.ie)
Date: Mon 14 Feb 2000 - 09:22:50 GMT
On Fri, Feb 11, 2000 at 05:10:59PM -0000, Ciaran Bradley mentioned:
> The plan has since changed 'cos we're running out of time, so I'm using
> Oracle WebDb 2.0 and Oracle 8.05 to speed things up a bit. I've managed to
> get Oracle8 and WebDb up and running but, now I'm running into some network
> errors in WebDb that I don't really understand. I was hoping someone here
> might be able to help. The error message I'm getting in Netscape when
> connecting to parts of WebDb is "Network error: broken pipe". What exactly
> is a broken pipe?
A pipe is a method of ferrying info from a data producer, to a data
consumer. The "pipe" has a fixed volume. When it's filled by the producer,
the OS stops the producer, and schedules the consumer. The consumer is let
run till the pipe is empty, or it calls "schedule()", which usually starts
another process running.
So, a "broken pipe" is either when the data source aborts without sending
and "End of File", or EOF to the pipe. Over a network, this can also mean
that the network connection was broken. The OS can't "make up" an EOF, so
it usually sends the client a SIGIO signal. Run strace on the program
that gets the broken pipe, and look through the output for a SIGIO to
confirm that's what's happening. If it is, checkout what's happened the
server.
Kate
This archive was generated by hypermail 2.1.6 : Thu 06 Feb 2003 - 13:05:25 GMT