Date: Fri, 13 May 2022 11:22:20 -0400
From: Chet Ramey <chet.ra...@case.edu>
Message-ID: <a90562c2-c917-fc76-b515-9f69868f0...@case.edu>
| Show your work.
|
| I tested this on macOS 12 and RHEL 7, using interactive shells with job
| control enabled,
That is likely the difference. The question was about what happens when
job control is not enabled.
When job control is enabled, the kill kills that job's process group, and
all of it gets signalled. Without job control, that's not possible, the
shell can only kill its known children, their children (absent relaying of
the signal down the tree) never see it.
I no longer remember the exact command I used (cannot even locate the message
you're quoting from), which caused bash to fork a sub-shell, in which to
run the pipeline, rather than running it directly from the parent - but
that's not really the point, doing that was not wrong, whatever provoked it,
it simply meant that the parent shell did not know the actual processes
running in the pipe, so could not do anything to them.
kre
