Path: csiph.com!goblin1!goblin.stu.neva.ru!usenet.stanford.edu!not-for-mail
From: Robert Elz <kre@munnari.OZ.AU>
Newsgroups: gnu.bash.bug
Subject: Re: signals ignored in a subshell
Date: Mon, 06 Apr 2020 20:25:26 +0700
Lines: 17
Approved: bug-bash@gnu.org
Message-ID: <mailman.247.1586179565.2644.bug-bash@gnu.org>
References: <CAH7i3Lo_vDKahPLAgCvuPXw-TbgfgKt9OeJw-Ki2nja+ew-nDg@mail.gmail.com> <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> <11149.1586179526@jinx.noi.kre.to>
NNTP-Posting-Host: lists.gnu.org
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Trace: usenet.stanford.edu 1586179565 17781 209.51.188.17 (6 Apr 2020 13:26:05 GMT)
X-Complaints-To: action@cs.stanford.edu
Cc: "chet.ramey@case.edu" <chet.ramey@case.edu>, "bug-bash@gnu.org" <bug-bash@gnu.org>
To: =?UTF-8?B?T8SfdXo=?= <oguzismailuysal@gmail.com>
Envelope-to: bug-bash@gnu.org
In-Reply-To: <CAH7i3Lo_vDKahPLAgCvuPXw-TbgfgKt9OeJw-Ki2nja+ew-nDg@mail.gmail.com>
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [generic]
X-Received-From: 2001:3c8:9009:181::2
X-BeenThere: bug-bash@gnu.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Bug reports for the GNU Bourne Again SHell <bug-bash.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/bug-bash>, <mailto:bug-bash-request@gnu.org?subject=unsubscribe>
List-Archive: <https://lists.gnu.org/archive/html/bug-bash>
List-Post: <mailto:bug-bash@gnu.org>
List-Help: <mailto:bug-bash-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/bug-bash>, <mailto:bug-bash-request@gnu.org?subject=subscribe>
X-Mailman-Original-Message-ID: <11149.1586179526@jinx.noi.kre.to>
X-Mailman-Original-References: <CAH7i3Lo_vDKahPLAgCvuPXw-TbgfgKt9OeJw-Ki2nja+ew-nDg@mail.gmail.com> <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>
Xref: csiph.com gnu.bash.bug:16098

    Date:        Mon, 6 Apr 2020 15:06:02 +0300
    From:        =?UTF-8?B?T8SfdXo=?= <oguzismailuysal@gmail.com>
    Message-ID:  <CAH7i3Lo_vDKahPLAgCvuPXw-TbgfgKt9OeJw-Ki2nja+ew-nDg@mail.gmail.com>

  | 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?

That would be correct.

kre

ps: the Subject of all of these messages is misleading, there hasn't
been an example where a subshell is involved.   There could be, but
none of the test cases for the various issues so far have invoked one.