This looks like a bug in the SIGCHLD handler of bash. It doesn't save
errno, therefore cluttering the errno value of whatever code was
interrupted by SIGCHLD.
But this bug only explains the unexpected error message, not why there
is an error.
-- Jan- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/