Normally pipes created by threaded apps are left non-blocking after being

closed so that a threaded child process can still read it without blocking.
However, leaving stdin/out/err non-blocking when closed is bad because it
can be shared with non-threaded apps that can't deal with a non-blocking
file descriptor (i.e. cat). Therefore special case stdin/out/err pipes so
that they are reset to blocking upon a close(). Tested by robert@, jolan@
and myself with multiple OOo builds on mp systems where the problem was
seen more frequently.

0 files changed, 0 insertions, 0 deletions