Custom Query (431 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (43 - 45 of 431)

Ticket Resolution Summary Owner Reporter
#556 fixed IZ2674: need a better way to control shadow daemon parameters templedf
Description

[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.
#621 fixed IZ2871: SGE_COMPLEX_ hook should be documented templedf
Description

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

        Issue #:      2871             Platform:     All      Reporter: templedf (templedf)
       Component:     gridengine          OS:        All
     Subcomponent:    man              Version:      6.2         CC:    None defined
        Status:       NEW              Priority:     P3
      Resolution:                     Issue type:    DEFECT
                                   Target milestone: ---
      Assigned to:    andreas (andreas)
      QA Contact:     andreas
          URL:
       * Summary:     SGE_COMPLEX_ hook should be documented
   Status whiteboard:
      Attachments:

     Issue 2871 blocks:
   Votes for issue 2871:


   Opened: Mon Jan 12 14:41:00 -0700 2009 
------------------------


The SGE_COMPLEX_ hook described in the workaround for Issue 409 should be
documented in the man page for qsub/qrsh.

   ------- Additional comments from templedf Mon Jan 12 14:58:27 -0700 2009 -------
I just tested this feature in 6.2, and it doesn't appear to work.  Perhaps this
should be a qsub issue instead.
#632 fixed IZ2906: JSV API needs to be available for Java platform templedf
Description

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

        Issue #:      2906             Platform:     All           Reporter: templedf (templedf)
       Component:     gridengine          OS:        All
     Subcomponent:    kernel           Version:      6.2u2            CC:    None defined
        Status:       STARTED          Priority:     P3
      Resolution:                     Issue type:    ENHANCEMENT
                                   Target milestone: ---
      Assigned to:    templedf (templedf)
      QA Contact:     andreas
          URL:
       * Summary:     JSV API needs to be available for Java platform
   Status whiteboard:
      Attachments:

     Issue 2906 blocks:
   Votes for issue 2906:


   Opened: Thu Feb 5 12:01:00 -0700 2009 
------------------------


Not sure what component to submit against...

The JSV feature includes an API for Perl, Tcl, and Borne shell.  The API should
also be available for the Java platform.  Java platform support would also
enable Python, Ruby, and JavaScript.  The Java platform has significant
performance advantages over Perl, Tcl, and especially Borne shell in server-side
JSV scripts.

   ------- Additional comments from templedf Thu Jun 11 12:12:29 -0700 2009 -------
Assigning it to myself.

   ------- Additional comments from templedf Thu Jun 11 12:13:11 -0700 2009 -------
I have an implementation.  It still needs thorough testing, though.
Note: See TracQuery for help on using queries.