Re: SIGTERM ignored before exec race

2013-03-25 Thread Pádraig Brady
On 02/18/2013 02:39 AM, Chet Ramey wrote: > On 2/17/13 7:46 PM, Pádraig Brady wrote: > I notice the following will wait for 5 seconds for the timeout process to end with SIGALRM, rather than immediately due to kill sending the SIGTERM. >>> >>> I think the way to approach this is to

Re: SIGTERM ignored before exec race

2013-03-25 Thread Chet Ramey
On 3/25/13 10:34 AM, Pádraig Brady wrote: > I've confirmed that bash 4.3 alpha doesn't have the issue. > Well I can't reproduce easily at least. > I didn't notice a NEWS item corresponding to it though. It's not a new feature. There are several items in CHANGES that refer to reworked signal hand

Re: SIGTERM ignored before exec race

2013-03-25 Thread Pádraig Brady
On 03/25/2013 02:55 PM, Chet Ramey wrote: > On 3/25/13 10:34 AM, Pádraig Brady wrote: > >> I've confirmed that bash 4.3 alpha doesn't have the issue. >> Well I can't reproduce easily at least. >> I didn't notice a NEWS item corresponding to it though. > > It's not a new feature. There are severa

"typeset +x var" to a variable exported to a function doesn't remove it from the environment.

2013-03-25 Thread Dan Douglas
Hello, $ function f { typeset +x x; typeset x=123; echo "$x"; sh -c 'echo "$x"'; }; x=abc f 123 abc $ echo "$BASH_VERSION" 4.2.45(1)-release This is inconsistent with a variable defined and exported any other way. (ksh93/mksh/zsh don't have this issue. Dash doesn't actually

Assignments preceding "declare" affect brace and pathname expansion.

2013-03-25 Thread Dan Douglas
Hi, $ set -x; foo=bar declare arr=( {1..10} ) + foo=bar + declare 'a=(1)' 'a=(2)' 'a=(3)' 'a=(4)' 'a=(5)' $ touch xy=foo $ declare x[y]=* + declare 'x[y]=*' $ foo=bar declare x[y]=* + foo=bar + declare xy=foo This isn't the same bug as the earlier a=([n]=*) i

A few possible process substitution issues

2013-03-25 Thread Dan Douglas
Hello, 1. Process substitution within array indices. The difference between (( 1<(2) )) and (( a[1<(2)] )) might be seen as surprising. Zsh and ksh don't do this in any arithmetic context AFAICT. Fun stuff: # print "moo" dev=fd=1 _[1<(echo moo >&2)]= # Fork bomb