[GE issues] [Issue 3017] New - inconsistent signal delivery behavior with and without -notify

joga Joachim.Gabler at sun.com
Tue May 5 10:13:30 BST 2009


http://gridengine.sunsource.net/issues/show_bug.cgi?id=3017
                 Issue #|3017
                 Summary|inconsistent signal delivery behavior with and without
                        | -notify
               Component|gridengine
                 Version|6.2beta
                Platform|All
                     URL|
              OS/Version|All
                  Status|NEW
       Status whiteboard|
                Keywords|
              Resolution|
              Issue type|DEFECT
                Priority|P2
            Subcomponent|execution
             Assigned to|pollinger
             Reported by|joga






------- Additional comments from joga at sunsource.net Tue May  5 02:13:28 -0700 2009 -------
We found one interesting thing in the signal delivery with SGE.

If we suspend a job submitted WITHOUT the -notify option, the SIGTSTP (we modified queue configuration so that it sends SIGTSTP instead of
SIGSTOP so that it can be caught) is sent to whole process group ( -PID).

But, if we suspend a job submitted WITH the -notify option, the SIGUSR1 was sent to the whole process group (-PID) and after the
notify_interval seconds, the SIGTSTP was sent to ONLY the parent process itself (PID), which is the job script.

Is there any reason that, when the -notify option was used, the "SIGTSTP" signal is sent to the parent process only?
Wouldn't it be more consistent to sent SIGTSTP to the whole process group?

------------------------------------------------------
http://gridengine.sunsource.net/ds/viewMessage.do?dsForumId=36&dsMessageId=190478

To unsubscribe from this discussion, e-mail: [issues-unsubscribe at gridengine.sunsource.net].



More information about the gridengine-users mailing list