11 messages in net.sunsource.gridengine.users[GE users] Ctrl-C behavior in Qrsh shell| From | Sent On | Attachments |
|---|---|---|
| richmaes | Oct 12, 2009 5:18 pm | |
| rayson | Oct 13, 2009 10:56 pm | |
| richmaes | Oct 14, 2009 10:07 am | |
| petrik | Oct 15, 2009 12:40 am | |
| richmaes | Oct 16, 2009 4:03 pm | |
| reuti | Oct 19, 2009 3:28 pm | |
| richmaes | Oct 20, 2009 9:29 am | |
| reuti | Oct 20, 2009 11:43 am | |
| richmaes | Oct 20, 2009 2:23 pm | |
| richmaes | Oct 20, 2009 2:40 pm | |
| sarman_1998 | Oct 22, 2009 10:59 am |
| Subject: | [GE users] Ctrl-C behavior in Qrsh shell | |
|---|---|---|
| From: | richmaes (rma...@ciena.com) | |
| Date: | Oct 12, 2009 5:18:21 pm | |
| List: | net.sunsource.gridengine.users | |
I have an issue where I have ported a LSF script over to the SGE environment.
The only outstanding issue I have right now is the behavior of Ctrl-C. When
running a program called IRun which is part of the NCSim tool suite, typcially
within an interactive LSF shell, we can hit Ctrl-C and drop down into a NC-Sim
menu. We can resume by typing . <enter>. It appears that using Ctrl-C when
using a qrsh invoked batch job, just results in having the PID terminated.
I think the signal that gets passed in when Ctrl-C is hit is getting intercepted
by the QRSH shell before the executing program.
I can't seem to find anything on the topic except an old bug that seemed to
indicate this may have worked in the past and was found to be a defect, so it
was fixed.
Is there a know solution for changing this behavior?
------------------------------------------------------ http://gridengine.sunsource.net/ds/viewMessage.do?dsForumId=38&dsMessageId=221310
To unsubscribe from this discussion, e-mail:
[user...@gridengine.sunsource.net].