Re: "wait" loses signals

From	Harald van Dijk <harald@gigawatt.nl>
Newsgroups	gnu.bash.bug
Subject	Re: "wait" loses signals
Date	2020-02-20 09:16 +0000
Message-ID	<mailman.1225.1582190832.2412.bug-bash@gnu.org> (permalink)
References	<9b9d435b-3d2f-99bd-eb3d-4a676ce8927d@gigawatt.nl> <750d460d-b8a4-4157-1488-9f4d9f973715@redhat.com> <35034c85-fd5a-5034-a2d5-e3903888069d@case.edu> <16027.1582163732@jinx.noi.kre.to> <ab007cd0-d98a-1faa-4765-2399f5df74db@gigawatt.nl>

Show all headers | View raw

On 20/02/2020 01:55, Robert Elz wrote:
>      Date:        Wed, 19 Feb 2020 23:53:56 +0000
>      From:        Harald van Dijk <harald@gigawatt.nl>
>      Message-ID:  <9b9d435b-3d2f-99bd-eb3d-4a676ce8927d@gigawatt.nl>
> 
> 
>    | POSIX says in the description of the trap command "Otherwise, the
>    | argument action shall be read and executed by the shell when one of the
>    | corresponding conditions arises." Because it says "when", not "after",
>    | if interpreted literally, it does not even allow waiting until the
>    | current command finishes executing.
> 
> You need to look at XCU 2.11 not just the description of the trap command
> itself.

Ah, thanks, that makes an exception for when the shell is waiting for a 
command to complete. It's the same as what bash documents. In that case, 
I think we can interpret the "when" in the description of the trap 
command literally except when 2.11 overrides it.

Cheers,
Harald van Dijk

Back to gnu.bash.bug | Previous | Next | Find similar

Thread

Re: "wait" loses signals Harald van Dijk <harald@gigawatt.nl> - 2020-02-20 09:16 +0000

csiph-web