Re: bash signal trap bug

2014-01-13 Thread Paweł Gołaszewski
On Mon, 13 Jan 2014, Chet Ramey wrote: > >> I have made several changes to the trap command processing, and > >> things in bash-4.3 should be closer to the way you want them to run. > > Can you give some patch/link? > The latest round of changes will be out on savannah in a couple of days > at mo

Re: bash signal trap bug

2014-01-13 Thread Chet Ramey
On 1/13/14 4:06 AM, Paweł Gołaszewski wrote: >> I have made several changes to the trap command processing, and things >> in bash-4.3 should be closer to the way you want them to run. > > Can you give some patch/link? The latest round of changes will be out on savannah in a couple of days at mo

Re: bash signal trap bug

2014-01-13 Thread Paweł Gołaszewski
On Sat, 11 Jan 2014, Chet Ramey wrote: > There are a few things going on here. First, after the first SIGHUP, > you are running the entire script from a trap handler. Bash treats > things in a trap handler context a little specially. > > Second, bash doesn't allow recursive trap invocations: i

Re: bash signal trap bug

2014-01-11 Thread Chet Ramey
On 1/8/14, 12:01 PM, Paweł Gołaszewski wrote: > Hello, > > I think I've found bug in signal handling in bash. > > Look at 2 scripts: > http://www.blues.gda.pl/SOURCES/show_logs.sh > http://www.blues.gda.pl/SOURCES/show_logs.zsh > > Both are identical. "zsh" version works fine, "bash" version doe

bash signal trap bug

2014-01-08 Thread Paweł Gołaszewski
Hello, I think I've found bug in signal handling in bash. Look at 2 scripts: http://www.blues.gda.pl/SOURCES/show_logs.sh http://www.blues.gda.pl/SOURCES/show_logs.zsh Both are identical. "zsh" version works fine, "bash" version doesn't. After start everything is fine, a can send _one_ HUP signa