On 2/12/21 1:51 AM, Koichi Murase wrote:
2021年2月12日(金) 4:27 Chet Ramey <chet.ra...@case.edu>:
Thank you. Yes, if there is a simpler but still robust and reliable
way to do it, that would be nice.
There is, in fact, a simpler way for this case. Blocking SIGCHLD around the
calls to zread and its siblings fixes the problem. It might not be enough
of a general solution for you, though.
Thank you for the fix. Now I see why this particular form (CMD & read
-t) < XXX caused a significantly large timeout-failure rate. But, I
guess the failure rate is almost zero but not exactly zero even after
this fix.
I can't reproduce the failure at all with the sigprocmask changes I added.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU c...@case.edu http://tiswww.cwru.edu/~chet/
