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

        Issue #:      2674             Platform:     All           Reporter: templedf (templedf)
       Component:     gridengine          OS:        All
     Subcomponent:    qmaster          Version:      6.2              CC:    None defined
        Status:       NEW              Priority:     P3
      Resolution:                     Issue type:    ENHANCEMENT
                                   Target milestone: ---
      Assigned to:    ernst (ernst)
      QA Contact:     ernst
          URL:
       * Summary:     need a better way to control shadow daemon parameters
   Status whiteboard:
      Attachments:

     Issue 2674 blocks:
   Votes for issue 2674:


   Opened: Wed Jul 23 04:45:00 -0700 2008 
------------------------


The shadow daemon behavior is controlled by a set of three environment
variables.  Because the shadow daemon is typically started by the
$SGE_ROOT/$SGE_CELL/common/sgemaster script during host initialization, there is
no way to set the variables before the script runs.  The current solution is to
edit the sgemaster file to set the variables before running the shadow daemon,
but that is a poor solution.

One solution would be to have a separate file in the common directory to set the
shadow daemon behavior.  Another solution would be to set the variables
explicitly at the top of the sgemaster script so that if one must edit the file,
it is obvious what to edit.

   ------- Additional comments from templedf Wed Jul 23 05:47:15 -0700 2008 -------
In the case of SMF, the above is the complete story.  Without SMF, it is
possible to also edit the RC script to add the environment variables.  The same
arguments apply, however.  In addition, both the SMF and non-SMF methods should
match, so I would discount editing the RC script as a real option.

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

        Issue #:      2675             Platform:     Sun       Reporter: dagru (dagru)
       Component:     gridengine          OS:        All
     Subcomponent:    install          Version:      6.2beta      CC:    None defined
        Status:       NEW              Priority:     P4
      Resolution:                     Issue type:    DEFECT
                                   Target milestone: ---
      Assigned to:    dom (dom)
      QA Contact:     dom
          URL:
       * Summary:     After installing the xterm is not found because the wrong path was set
   Status whiteboard:
      Attachments:

     Issue 2675 blocks:
   Votes for issue 2675:


   Opened: Thu Jul 24 01:54:00 -0700 2008 
------------------------


After installing on RHEL 5.2 the xterm binary is not found because the path
is wrong. One has to setup the path manually.

This can be fixed if further tests (if the binary exists)
and/or differentiations for different linux distros are
introduced in the arch_variables script.

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

        Issue #:      2686             Platform:     All      Reporter: mpospisil (mpospisil)
       Component:     gridengine          OS:        All
     Subcomponent:    clients          Version:      6.1u4       CC:    None defined
        Status:       NEW              Priority:     P3
      Resolution:                     Issue type:    DEFECT
                                   Target milestone: ---
      Assigned to:    mpospisil (mpospisil)
      QA Contact:     roland
          URL:
       * Summary:     qstat -j does not print array task information
   Status whiteboard:
      Attachments:

     Issue 2686 blocks:
   Votes for issue 2686:


   Opened: Mon Aug 11 13:26:00 -0700 2008 
------------------------


qstat -j does no longer print imformation about the array range. The line
"job-array tasks" is completely missing:

job was submitted with:
qsub -t 1-2 $SGE_ROOT/examples/jobs/sleeper.sh 100000

6.1u2:
qstat -j <job-id> | grep "job-array tasks"
job-array tasks:            1-2:1

6.1u4:
qstat -j <job-id> | grep "job-array tasks"
-> empty