Broken pipe

[Kenneth Brody]

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.

--
KenBrody at BestWeb dot net        spamtrap: <g8ymh8uf001 at sneakemail.com>
http://www.hvcomputer.com
http://www.fileProPlus.com