Opened 13 years ago

Last modified 11 years ago

#618 new enhancement

IZ2865: contact string interpretation should happen in japi_init()

Reported by: templedf Owned by:
Priority: lowest Milestone:
Component: sge Version: 6.1
Severity: Keywords: drmaa


[Imported from gridengine issuezilla]

        Issue #:      2865             Platform:     All           Reporter: templedf (templedf)
       Component:     gridengine          OS:        All
     Subcomponent:    drmaa            Version:      6.1              CC:    None defined
        Status:       NEW              Priority:     P5
      Resolution:                     Issue type:    ENHANCEMENT
                                   Target milestone: ---
      Assigned to:    dagru (dagru)
      QA Contact:     templedf
       * Summary:     contact string interpretation should happen in japi_init()
   Status whiteboard:

     Issue 2865 blocks:
   Votes for issue 2865:

   Opened: Mon Jan 5 13:18:00 -0700 2009 

The drmaa_init() function parses the contact string for settings.  The settings
that it is parsing, however, are not DRMAA-specific.  The parsing should
therefore be moved into the japi_init() function.

It is possible that future enhancements will result in the need for the
drmaa_init() function to parse DRMAA-specific contact string settings.  If that
happens, then the parsing will happen both in the drmaa_init() and japi_init()
functions, and care should be taken that any setting interpreted successfully by
drmaa_init() should be prevent from being reinterpreted by japi_init().

Change History (0)

Note: See TracTickets for help on using tickets.