Broken pipe

[Richard D. Williams]

Funny thing.  It turns out, by resetting the printer type, the Broke 
Pipe error is gone.
Thanks for all the response.

Richard

Kenneth Brody wrote:

>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
>_______________________________________________
>Filepro-list mailing list
>Filepro-list at lists.celestial.com
>http://mailman.celestial.com/mailman/listinfo/filepro-list
>
>
>
>  
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.celestial.com/pipermail/filepro-list/attachments/20060306/a8c01b73/attachment-0001.html