Re: Race condition in handling SIGHUP

2016-04-29 Thread Siteshwar Vashisht
- Original Message - > From: "Chet Ramey" > To: "Siteshwar Vashisht" , bug-bash@gnu.org > Cc: dkas...@redhat.com, "chet ramey" > Sent: Thursday, April 28, 2016 6:19:17 PM > Subject: Re: Race condition in handling SIGHUP > > On 4/27

Re: Race condition in handling SIGHUP

2016-04-28 Thread Chet Ramey
On 4/28/16 11:49 AM, David Kaspar [Dee'Kej] wrote: > I'm going to insert the missing verb into that sentence ("remove") and > answer "yes, we're going to try it and see how it goes." > > ​Yes, you have assumed it right that I missed the word "remove"... :)​ > > ​And I think it should be

Re: Race condition in handling SIGHUP

2016-04-28 Thread David Kaspar [Dee'Kej]
On Thu, Apr 28, 2016 at 5:35 PM, Chet Ramey wrote: > YP was the original one; now you have things like LDAP and other directory > services. Something you use when you don't want to have everyone in the > password file. These are somewhat out of favor now. > ​Yeah, I was thinking about LDAP, but

Re: Race condition in handling SIGHUP

2016-04-28 Thread David Kaspar [Dee'Kej]
On Thu, Apr 28, 2016 at 2:49 PM, Chet Ramey wrote: > Because systems using a networked password database can hang at a priority > that doesn't interrupt the system call when a SIGHUP arrives. > ​I'm sorry, but what exactly do you mean by 'networked password database'? I'm not sure I follow you co

Re: Race condition in handling SIGHUP

2016-04-28 Thread Chet Ramey
On 4/28/16 11:23 AM, David Kaspar [Dee'Kej] wrote: > On Thu, Apr 28, 2016 at 2:49 PM, Chet Ramey > wrote: > > Because systems using a networked password database can hang at a priority > that doesn't interrupt the system call when a SIGHUP arrives. > > ​I'm so

Re: Race condition in handling SIGHUP

2016-04-28 Thread Chet Ramey
On 4/27/16 6:04 AM, Siteshwar Vashisht wrote: > While this issue was fixed by backporting somes changes (See attached > patch) from [4] to bash-4.2 or older versions, there is still a corner > case which may cause race condition in handling SIGHUP in current upstream. > > &#x

Race condition in handling SIGHUP

2016-04-27 Thread Siteshwar Vashisht
rom user), and ~/.bash_history will not be updated. We started seeing this bug after above mentioned patch was backported to RHEL 6. Sometimes ~/.bash_history is not updated when user executes 'reboot' command in a ssh session. This is caused by race condition in handling SIGHUP.

Race condition in handling SIGHUP

2016-04-27 Thread Siteshwar Vashisht
rom user), and ~/.bash_history will not be updated. We started seeing this bug after above mentioned patch was backported to RHEL 6. Sometimes ~/.bash_history is not updated when user executes 'reboot' command in a ssh session. This is caused by race condition in handling SIGHUP.