On Wed, 2002-05-22 at 00:33, Chris Fedde wrote: > I saw behavior like this with 0.18 on FreeBSD 4.5 and Solaris 2.8. > After 0.19 the sigchld consistently arrives after two error events > marking failed nonblocking read on stderr and stdout.
Unfortunately, I don't share the same experience. I observe the following sequence read error with error number 0 sigchild 2nd read error with error number 0 Apparently, the first read error comes from STDERR, and the second one is STDOUT. My current kludge is to count the number of read errors. When two of them are received, one can be assured that both STDERR and STDOUT are flushed. This approach was suggested on the mailing list last December as well. > To my knowledge > there is still no way to map the error events back to file handles. Let me make sure I understand this. Do you mean there is no way to know which file handle caused the read error? Pete
