On Wed, Dec 17, 2014 at 2:34 PM, Jiri Kukacka <jiri.kuka...@oracle.com> wrote: > > I investigated the bug, and I found that this happens when machine is too > slow to send SIGHUP. This also happens when I open a terminal in GUI, and > close the window (click X). To simulate this, one can just open XTerm > window, ssh to any machine (even localhost), create a process tree long > enough (just run bash in bash, depth of 6 was usually enough), type > something like 'touch /tmp/thisShouldntExists' and close the window with > terminal. Then in /tmp a file named thisShouldntExists appears. This is just > a nondestructive test case, a a destructive one is noted above.
what I did (bash 4.3.30): 1. two cores machine, loaded both cores 100% 2. logged in via ssh with xterm -e ssh xxxx 3. ran su - 16 times, each su - in the previous session created with su - 4. typed touch /tmp/noway 5. closed the xterm the file did not appear. can you copy-paste the exact replication scenario? possibly with the script that triggers it for you? do you also need to fill the pending signals queue? I cant imagine how slow the machine should be to not be able to deliver the signal on time? cheers, pg
