Path: csiph.com!goblin1!goblin.stu.neva.ru!usenet.stanford.edu!not-for-mail
From: =?UTF-8?B?T8SfdXo=?= <oguzismailuysal@gmail.com>
Newsgroups: gnu.bash.bug
Subject: Re: signals ignored in a subshell
Date: Mon, 6 Apr 2020 15:06:02 +0300
Lines: 47
Approved: bug-bash@gnu.org
Message-ID: <mailman.241.1586174767.2644.bug-bash@gnu.org>
References: <CAH7i3LqUZcV6shJv6nQoRkLp-zhBgTpWaUPKdzZwVC-W_0e8yw@mail.gmail.com> <23276.1586024838@jinx.noi.kre.to> <CAH7i3Lr5TTK+N-qC39+nmSo7jjhzDvPux39N4i2MyP5LCnnv5w@mail.gmail.com> <16086.1586068489@jinx.noi.kre.to> <CAH7i3LrwPy9J9+8BPgvT+BGtv39nQJ2H-prxWXu7mHYZ8UjodQ@mail.gmail.com> <45c766ba-4489-bd7b-40c7-32fed37461f9@case.edu> <CAH7i3Lr5zBub6yObXkwV78E0Oyct-bAu2+D2hocpT8NNyBqHLg@mail.gmail.com> <CAH7i3Lo_vDKahPLAgCvuPXw-TbgfgKt9OeJw-Ki2nja+ew-nDg@mail.gmail.com>
NNTP-Posting-Host: lists.gnu.org
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Cc: Robert Elz <kre@munnari.oz.au>, "bug-bash@gnu.org" <bug-bash@gnu.org>
To: "chet.ramey@case.edu" <chet.ramey@case.edu>
Envelope-to: bug-bash@gnu.org
In-Reply-To: <CAH7i3Lr5zBub6yObXkwV78E0Oyct-bAu2+D2hocpT8NNyBqHLg@mail.gmail.com>
Precedence: list
Xref: csiph.com gnu.bash.bug:16095

Or, is it that when job controls are enabled each synchronous command is
run in its own process group and SIGINT is not sent to the shell at all?

6 Nisan 2020 Pazartesi tarihinde O=C4=9Fuz <oguzismailuysal@gmail.com> yazd=
=C4=B1:

> That's not how read is defined to behave. wait has special wording defini=
ng
>> what happens when it receives a signal. Bash default mode behaves as I
>> described previously -- trapping the signal and returning from the handl=
er
>> 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=C4=9Fuz
>
>

--=20
O=C4=9Fuz