[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
signals ignored in a subshell
From: |
Oğuz |
Subject: |
signals ignored in a subshell |
Date: |
Mon, 6 Apr 2020 15:03:45 +0300 |
>
> That's not how read is defined to behave. wait has special wording defining
> what happens when it receives a signal. Bash default mode behaves as I
> described previously -- trapping the signal and returning from the handler
> results in the read being restarted -- and posix mode will run the trap
> handler before returning from the `read' builtin.
>
Okay, you're right, in posix mode the behavior is as expected. However I
still didn't get why job controls being enabled/disabled changes the way an
interactive shell handles signals in posix mode. Like
$ set -o posix
$
$ trap 'echo foo' INT
$
$ read
^Cfoo
$ sleep 5
^C
$
$ set +m
$
$ read
^Cfoo
$ sleep 5
^Cfoo
Is there a race condition here or does posix mandate this behavior for
built-in utilities?
--
Oğuz
- signals ignored in a subshell, Oğuz, 2020/04/04
- Re: signals ignored in a subshell, Robert Elz, 2020/04/04
- Re: signals ignored in a subshell, Oğuz, 2020/04/04
- Re: signals ignored in a subshell, Robert Elz, 2020/04/05
- Re: signals ignored in a subshell, Oğuz, 2020/04/05
- Re: signals ignored in a subshell, Chet Ramey, 2020/04/05
- signals ignored in a subshell,
Oğuz <=
- Re: signals ignored in a subshell, Oğuz, 2020/04/06
- Re: signals ignored in a subshell, Chet Ramey, 2020/04/06
- Re: signals ignored in a subshell, Robert Elz, 2020/04/06
- Re: signals ignored in a subshell, Robert Elz, 2020/04/06
- Re: signals ignored in a subshell, Chet Ramey, 2020/04/06
- Re: signals ignored in a subshell, Robert Elz, 2020/04/06
- Re: signals ignored in a subshell, Chet Ramey, 2020/04/06
- Re: signals ignored in a subshell, Robert Elz, 2020/04/06
Re: signals ignored in a subshell, Chet Ramey, 2020/04/05