Custom Query (1181 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (190 - 192 of 1181)

Ticket Resolution Summary Owner Reporter
#695 fixed IZ3079: Man page entry for SCHEDULER_TIMEOUT incorrectly states that default is 600 jf222792
Description

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

        Issue #:      3079             Platform:     Sun      Reporter: jf222792 (jf222792)
       Component:     gridengine          OS:        All
     Subcomponent:    man              Version:      6.2u2       CC:    None defined
        Status:       NEW              Priority:     P3
      Resolution:                     Issue type:    DEFECT
                                   Target milestone: ---
      Assigned to:    jf222792 (jf222792)
      QA Contact:     andreas
          URL:
       * Summary:     Man page entry for SCHEDULER_TIMEOUT incorrectly states that default is 600
   Status whiteboard:
      Attachments:

     Issue 3079 blocks:
   Votes for issue 3079:


   Opened: Wed Jul 8 07:24:00 -0700 2009 
------------------------


SGE_CONF(5) in 6.2u2_RC2, under qmaster_params:

     SCHEDULER_TIMEOUT
          Setting this parameter allows the scheduler  GDI  event
          acknowledge  timeout  to  be  manually  configured to a
          specific value. Currently the default value is  set  to
          10 minutes. The SCHEDULER_TIMEOUT value is specified in
          seconds.

This is slightly misleading. The default value is 10 minutes with
default scheduler configuration, but the default depends on the scheduler configuration.

More precisely, the default value for the SCHEDULER_TIMEOUT is 10 times the event delivery interval, capped between 600 and 1200 seconds.
*** (#1 of 1): 2009-02-18 14:07:15 CET thomas.dehn@sun.com
#700 fixed IZ3089: JSV Protocol is not handled correctly in client JSV ernst
Description

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

        Issue #:      3089             Platform:     All      Reporter: ernst (ernst)
       Component:     gridengine          OS:        All
     Subcomponent:    clients          Version:      6.2u2       CC:    None defined
        Status:       NEW              Priority:     P4
      Resolution:                     Issue type:    DEFECT
                                   Target milestone: ---
      Assigned to:    roland (roland)
      QA Contact:     roland
          URL:
       * Summary:     JSV Protocol is not handled correctly in client JSV
   Status whiteboard:
      Attachments:

     Issue 3089 blocks:
   Votes for issue 3089:


   Opened: Tue Jul 21 05:10:00 -0700 2009 
------------------------


The JSV Protocol is not handled correctly in client JSV. As a result the
shutdown of the JSV is not triggered. Therfore client JSVs will never get a
QUIT command.

For the JSV templates that are part of GE this is no problem because they
terminate also if the get an EOF of stdin.
#704 fixed IZ3095: add "-pty <yes|no>" switch to qsub pollinger
Description

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

        Issue #:      3095             Platform:     All           Reporter: pollinger (pollinger)
       Component:     gridengine          OS:        All
     Subcomponent:    clients          Version:      6.2              CC:    None defined
        Status:       NEW              Priority:     P2
      Resolution:                     Issue type:    ENHANCEMENT
                                   Target milestone: ---
      Assigned to:    roland (roland)
      QA Contact:     roland
          URL:
       * Summary:     add "-pty <yes|no>" switch to qsub
   Status whiteboard:
      Attachments:

     Issue 3095 blocks:
   Votes for issue 3095:


   Opened: Mon Aug 3 04:37:00 -0700 2009 
------------------------


In order to be able to execute batch jobs that need a pty, the "-pty <yes|no>" switch has to be added to qsub and the existing pty
functionality in the sge_shepherd for interactive jobs has to be extended for batch jobs.

In order to preserve the current behaviour, "-pty no" has to be the default.
Note: See TracQuery for help on using queries.