: The program below demonstrates what I believe is a Linux bug. It
: starts a child process and starts reading the child's standard output.
: It exits when it receives a SIGCHLD signal indicating that the child
: has exited. It seems to me that this signal should not be received
: until end of file is received on the child's standard output.
But why do you think so?
I am not aware of any norm or standard that would prescribe
such an ordering of events.
Andries