Opened 12 years ago

Last modified 9 years ago

#431 new defect

IZ2271: setpgrp fails in script if run too early

Reported by: templedf Owned by:
Priority: normal Milestone:
Component: sge Version: 6.1
Severity: minor Keywords: clients
Cc:

Description (last modified by admin)

[Imported from gridengine issuezilla http://gridengine.sunsource.net/issues/show_bug.cgi?id=2271]

   Issue #: 2271   Platform: All   Reporter: templedf (templedf)
   Component: gridengine   OS: All
   Subcomponent: clients   Version: 6.1   CC: None defined
   Status: NEW   Priority: P3
   Resolution:   Issue type: DEFECT
     Target milestone: ---
   Assigned to: roland (roland)
   QA Contact: roland
   URL:
   * Summary: setpgrp fails in script if run too early
   Status whiteboard:
   Attachments:
   Date/filename:                        Description:                                                                                                            Submitted by:
   Thu May 31 17:16:00 -0700 2007: sl.sh This is the script I'm using for my jobs (text/plain)                                                                   templedf
   Thu May 31 17:16:00 -0700 2007: out2  This is what a successful run looks like (text/plain)                                                                   templedf
   Thu May 31 17:17:00 -0700 2007: out   This is what a failed run looks like. The difference is that I commented out the sleep call in the script. (text/plain) templedf
     Issue 2271 blocks:
   Votes for issue 2271:

   Opened: Thu May 31 17:15:00 -0700 2007 
------------------------


In preparing for an advanced admin class, I was playing with jobs with processes
which escape the process group.  As my job, I'm using a script that does a
setpgrp call to create a new process group.  I found that the setpgrp call will
silently fail unless I delay a little before the call.  I do not see the problem
if I run the script directly from the command line.  I have run into the problem
with both qrsh and qsub.

I will attach the script and the output from a success and a failed run.  By
looking at the script and the output files, the problem should be clear.

   ------- Additional comments from templedf Thu May 31 17:16:30 -0700 2007 -------
Created an attachment (id=110)
This is the script I'm using for my jobs

   ------- Additional comments from templedf Thu May 31 17:16:58 -0700 2007 -------
Created an attachment (id=111)
This is what a successful run looks like

   ------- Additional comments from templedf Thu May 31 17:17:42 -0700 2007 -------
Created an attachment (id=112)
This is what a failed run looks like.  The difference is that I commented out the sleep call in the script.

Attachments (3)

110 (351 bytes) - added by dlove 9 years ago.
111 (875 bytes) - added by dlove 9 years ago.
112 (5.0 KB) - added by dlove 9 years ago.

Download all attachments as: .zip

Change History (4)

Changed 9 years ago by dlove

Changed 9 years ago by dlove

Changed 9 years ago by dlove

comment:1 Changed 9 years ago by admin

  • Description modified (diff)
  • Severity set to minor
  • Summary changed from IZ2271: fails in script if run too early to IZ2271: setpgrp fails in script if run too early
Note: See TracTickets for help on using tickets.