Broken pipe

[Fairlight]

On Mon, Mar 06, 2006 at 03:56:07PM -0500, after drawing runes in goat's blood,
Kenneth Brody cast forth these immortal, mystical words:
> Quoting Fairlight (Mon, 6 Mar 2006 15:39:02 -0500):
> [...]
> > In general, what generates SIGPIPE (Broken Pipe) is either writing to
> > or reading from the file descriptors of another process, a named pipe,
> > or socket, and having that process, named pipe, or socket disappear
> > before an attempt at another I/O operation is attempted.  The "pipe"
> > is no longer present, and the signal is generated because there's in
> > effect nothing left to talk to--nothing is holding the other end of
> > the line, so to speak.
> [...]
> 
> Actually, this only happens to the writing end if the reading end has
> been closed.  If the writing end is closed, the reading end simply
> sees EOF.

More or less goes without saying, but you're right now I think about it
some more.  I guess the recent centericq thing confused me a bit, as I
wouldn't have been sending anything to those connections (say, MSN) and it
would just give a broken pipe seemingly out of nowhere.

After looking at what you wrote though, I don't dispute it.

mark->