Koichi Nakashima

Thank you for taking time for this issue. I tried various things on bosh 2020/10/07. When I specified a non-existent process ID, wait would return 127, as I expected. This issue seems to have been fixed. $ wait 98765 $ echo $? 127 The following code returns 0 instead of 12, unlike I expected (It was same on bosh 2020/09/03). ( sleep 1; exit 12 ) & sleep 3 wait "$!" echo $? # => 0 The following code will stuck on bosh 2020/10/07 (It was works on bosh 2020/09/03). main() { sleep 3 & PID1=$! sleep 3...

Sorry. Let me confirm again. From https://pubs.opengroup.org/onlinepubs/9699919799/utilities/wait.html EXAMPLES Although the exact value used when a process is terminated by a signal is unspecified, if it is known that a signal terminated a process, a script can still reliably determine which signal by using kill as shown by the following script: sleep 1000& pid=$! kill -kill $pid wait $pid echo $pid was terminated by a SIG$(kill -l $?) signal. I agree that we can't expect the exit status to be 143...

Thank you for the detailed explanation! I wondered what had happened because the number of 208 was unfamiliar to me. There are no problem. Thank you!

bosh: I got unexpected exit status from "wait"

OK. Thank you for letting me know.

bosh: export is not inherited

Oh, I'm sorry. I forgot to check this ticket. It seems to work in the simple case above. However, please note that I have not tried it in complicated cases.

Problem when command substitution with redirection