> Next thing I am going to do is instrument my init to log the pid of all
> the children it waited for. That will hopefully isolate the bug a little
> and give me a lead to the exact race condition. I'll keep you posted.
No, init does not see the child.. So either somehow the kernel does the
right thing and returns the wrong exit code -- which, by looking at the
code, doesn't seem likely, but it's the next thing I will play with anyway
-- or the child is somehow mishandled due to some race condition and gets
"lost"..
Ion
--
It is better to keep your mouth shut and be thought a fool,
than to open it and remove all doubt.
-
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/