Re: SIGTERM ignored before exec race

2013-03-28 Thread Pádraig Brady
On 03/26/2013 03:23 PM, Chet Ramey wrote: > On 3/25/13 6:45 PM, Pádraig Brady wrote: > >> OK thanks for the pointer. >> So the race is narrowed rather than closed? >> As we have: >> >> execute_disk_command() >> { >> int pid = fork(); >> if (pid == 0) /* child */ >> { >>CHECK_SIGTER

Re: SIGTERM ignored before exec race

2013-03-26 Thread Chet Ramey
On 3/25/13 6:45 PM, Pádraig Brady wrote: > OK thanks for the pointer. > So the race is narrowed rather than closed? > As we have: > > execute_disk_command() > { > int pid = fork(); > if (pid == 0) /* child */ > { >CHECK_SIGTERM; /* Honor received SIGTERM. */ >do stuff; >

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

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 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-02-17 Thread Chet Ramey
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 change the SIGTERM handling from >> straight SIG_IG

Re: SIGTERM ignored before exec race

2013-02-17 Thread Pádraig Brady
On 02/17/2013 10:00 PM, Chet Ramey wrote: On 2/9/13 12:02 AM, Pádraig Brady wrote: $ rpm -q kernel glibc bash kernel-2.6.40.4-5.fc15.x86_64 glibc-2.14.1-6.x86_64 bash-4.2.10-4.fc15.x86_64 I notice the following will wait for 5 seconds for the timeout process to end with SIGALRM, rather than imm

Re: SIGTERM ignored before exec race

2013-02-17 Thread Chet Ramey
On 2/9/13 12:02 AM, Pádraig Brady wrote: > $ rpm -q kernel glibc bash > kernel-2.6.40.4-5.fc15.x86_64 > glibc-2.14.1-6.x86_64 > bash-4.2.10-4.fc15.x86_64 > > I notice the following will wait for 5 seconds for > the timeout process to end with SIGALRM, rather than > immediately due to kill sending

Re: SIGTERM ignored before exec race

2013-02-14 Thread Chet Ramey
On 2/9/13 12:02 AM, Pádraig Brady wrote: > $ rpm -q kernel glibc bash > kernel-2.6.40.4-5.fc15.x86_64 > glibc-2.14.1-6.x86_64 > bash-4.2.10-4.fc15.x86_64 > > I notice the following will wait for 5 seconds for > the timeout process to end with SIGALRM, rather than > immediately due to kill sending

Re: SIGTERM ignored before exec race

2013-02-11 Thread Pádraig Brady
On 02/10/2013 08:30 PM, Chet Ramey wrote: On 2/9/13 12:02 AM, Pádraig Brady wrote: $ rpm -q kernel glibc bash kernel-2.6.40.4-5.fc15.x86_64 glibc-2.14.1-6.x86_64 bash-4.2.10-4.fc15.x86_64 I notice the following will wait for 5 seconds for the timeout process to end with SIGALRM, rather than imm

Re: SIGTERM ignored before exec race

2013-02-10 Thread Chet Ramey
On 2/9/13 12:02 AM, Pádraig Brady wrote: > $ rpm -q kernel glibc bash > kernel-2.6.40.4-5.fc15.x86_64 > glibc-2.14.1-6.x86_64 > bash-4.2.10-4.fc15.x86_64 > > I notice the following will wait for 5 seconds for > the timeout process to end with SIGALRM, rather than > immediately due to kill sending