I have seen similar things happen here. Often in my case, it tends to
happen after Ive spawned more than one process from an xterm. Sometimes,
I can run a program from within an xterm, continue using that terminal for
some time, then if/when I close the xterm, sometimes every process it
started will terminate too.
This is intermittent though. If I start a process, for example with
"opera &", then hit Ctl-D, then opera stays running. However if I start
the process, then edit a couple of files, move some files/directories, etc
(general usage), then close the xterm, then opera will close too.
This problem has only persisted for me in X so far, however I just
experienced it in console mode too. I had started a program (junkbuster)
running as a background process, then went to edit a file. After I quit
vi, I had lost my controlling terminal. strace on the bash process showed
it sitting wait()'ing for something (not sure what) to return. I killed
junkbuster, and my prompt came back. I then re-ran junkbuster with the
previous command, it started properly, and returned me to a prompt.
I have also had another instance, when I had a loop running.. basically
$ while ( sleep 5s ); do ls ; done
When I hit Ctl-C, the loop stopped, bash silently crashed, and I was
returned to a login prompt. In the past, hitting Ctl-C sent a SIGINT to
the 'sleep' process, which then caused 'while' to fail and return to a
bash prompt.
These bugs have only appeared (for me), with the change to 3.0-16
Hope this helps
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
