So it is
too late to change the default.)
Signed-off-by: Ian Jackson
Signed-off-by: Ian Jackson
CC: Ian Campbell
---
MANIFEST| 3 +++
builtins/shopt.def | 2 ++
doc/bash.1 | 10 ++
doc/bashref.texi| 13 -
execute_cmd.c
Ian Jackson writes ("Re: Want way to run background processes with SIGINT
unignored"):
> Chet Ramey writes ("Re: Want way to run background processes with SIGINT
> unignored"):
> > This is the behavior that any new option would toggle. Some name like
> > `a
Chet Ramey writes ("Re: Want way to run background processes with SIGINT
unignored"):
> On 10/9/15 2:42 PM, Ian Jackson wrote:
> > However, it would be very easy for bash to provide an option (via `set
> > -o' perhaps) to disable this behaviour. That is, to al
Hi.
I've been wrestling recently[1] with a bash script which invokes a
number of subprocesses in parallel and collects the output. The
problem is that if you ^C the script, the subprocesses carry on
running. This is because of the standards-mandated resetting of
SIGINT (and QUIT) to SIG_IGN in c
Chet Ramey writes ("Re: Shellshock-vulnerable version still most obvious on
ftp.gnu.org"):
> On 11/6/14, 7:47 AM, Ian Jackson wrote:
> > But in the current environment it's looking rather quaint. We could
> > probably provide a full tarball for each patch release.
&
Chet Ramey writes ("Re: Shellshock-vulnerable version still most obvious on
ftp.gnu.org"):
> I will put tarballs with patches in the usual places within a few days.
Thanks, that would be very helpful.
For the future, it might be worth considering whether it's really
sensible, nowadays, to be dis
If you go to ftp://ftp.gnu.org/pub/gnu/bash/, the most obvious most
recent version of bash is this:
ftp://ftp.gnu.org/pub/gnu/bash/bash-4.3.tar.gz
ftp://ftp.gnu.org/pub/gnu/bash/bash-4.3.tar.gz.sig
The shellshock fix is hidden in a subdirectory:
ftp://ftp.gnu.org/pub/gnu/bash/bash-4.3-patches
