From 6732f0277455ff8d8c6a09261490377890dc986d Mon Sep 17 00:00:00 2001
From: izabera
Date: Wed, 22 Jun 2016 22:43:53 +0200
Subject: [PATCH] fix a couple of bugs in print_cmd.c
1. print all heredoc headers before printing their contents
2. don't print all the heredocs after any other redir
sample
BASH PATCH REPORT
=
Bash-Release: 4.3
Patch-ID: bash43-046
Bug-Reported-by:Sergey Tselikh
Bug-Reference-ID: <20150816110235.91f3e12e3f20d20cdaad9...@gmail.com>
Bug-Reference-URL:
http://lists.gn
BASH PATCH REPORT
=
Bash-Release: 4.3
Patch-ID: bash43-045
Bug-Reported-by:Basin Ilya
Bug-Reference-ID: <5624c0ac.8070...@gmail.com>
Bug-Reference-URL:
http://lists.gnu.org/archive/html/bug-bash
BASH PATCH REPORT
=
Bash-Release: 4.3
Patch-ID: bash43-044
Bug-Reported-by:Ondrej Oprala
Bug-Reference-ID: <539ed55b.2080...@redhat.com>
Bug-Reference-URL:
http://lists.gnu.org/archive/html/bug-
BASH PATCH REPORT
=
Bash-Release: 4.3
Patch-ID: bash43-043
Bug-Reported-by:lolilolicon
Bug-Reference-ID:
Bug-Reference-URL:
http://lists.gnu.org/archive/html/bug-bash/2014-08/msg00040.html
Bu
> Am 22.06.2016 um 11:34 schrieb John Lawlor :
>
> Hi,
>
> I came across some unusual behaviour in bash using the ‘-c’ parameter.
>
> If I do the following:
>
> bash -c "ping 127.0.0.1 > $HOME/console.log" &
>
> This starts two processes bash and ping:
>
> john 18038 17951 0 09:26
On Wed, Jun 22, 2016 at 10:34:59AM +0100, John Lawlor wrote:
> If I do the following:
>
> bash -c "ping 127.0.0.1 > $HOME/console.log" &
> Now if I kill bash:
>
> Bash is killed but not the child ping process. I was expecting that to be
> killed also.
Not a bug. If you want a signal (e.g. SI
Hi,
I came across some unusual behaviour in bash using the '-c' parameter.
If I do the following:
bash -c "ping 127.0.0.1 > $HOME/console.log" &
This starts two processes bash and ping:
john 18038 17951 0 09:26 pts/14 00:00:00 bash -c ping 127.0.0.1 >
/home/john/console.log
john 1
