-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 5/5/12 12:28 AM, Mike Frysinger wrote: > On Friday 04 May 2012 16:17:02 Chet Ramey wrote: >> On 5/4/12 2:53 PM, Mike Frysinger wrote: >>> it might be a little racy (wrt checking cnt >= 10 and then doing a wait), >>> but this is good enough for some things. it does lose visibility into >>> which pids are live vs reaped, and their exit status, but i more often >>> don't care about that ... >> >> What version of bash did you test this on? Bash-4.0 is a little different >> in how it treats the SIGCHLD trap. > > bash-4.2_p28. wait returns 145 (which is SIGCHLD).
I wonder if you were running in Posix mode. Posix says "When the shell is waiting, by means of the wait utility, for asynchronous commands to complete, the reception of a signal for which a trap has been set shall cause the wait utility to return immediately with an exit status >128, immediately after which the trap associated with that signal shall be taken." The trapped SIGCHLD has to force `wait' to return. - -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ``Ars longa, vita brevis'' - Hippocrates Chet Ramey, ITS, CWRU c...@case.edu http://cnswww.cns.cwru.edu/~chet/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk+nyVEACgkQu1hp8GTqdKuKfgCgi1B9wyK1IbVGxWrmkIz4BgDj +4EAn25jL8YlSjp3VWBseFqwjNWWpWxk =/unM -----END PGP SIGNATURE-----