Opened 16 years ago

Last modified 9 years ago

#104 new feature

IZ602: have default path for -@ options files

Reported by: chaubal Owned by:
Priority: normal Milestone:
Component: sge Version: 5.3
Severity: Keywords: clients
Cc:

Description

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

        Issue #:      602              Platform:     All       Reporter: chaubal (chaubal)
       Component:     gridengine          OS:        All
     Subcomponent:    clients          Version:      5.3          CC:    None defined
        Status:       NEW              Priority:     P3
      Resolution:                     Issue type:    FEATURE
                                   Target milestone: ---
      Assigned to:    andreas (andreas)
      QA Contact:     roland
          URL:
       * Summary:     have default path for -@ options files
   Status whiteboard:
      Attachments:

     Issue 602 blocks:
   Votes for issue 602:  1


   Opened: Tue Sep 9 09:12:00 -0700 2003 
------------------------


The -@ <optionsfile> flag to qsub is a handy way
to encapsulate multiple request options into one
place.  Currently, you have to specify the full
path to the file.

However, if there were a default path (eg,
$SGE_ROOT/$SGE_CELL/common/options/), then the
admin could create a set of prescribed options
files with the right combination of request
options, and users would need only to specify a
single name for each different job type.

Ideally, this could be done in a way in which the
options directory needs only to exist on the
master host (eg, qmaster checks for the specified
file and rejects the "qsub" if not found).
Otherwise this would include yet another
dependency on file-sharing, which should be
avoided as much as possible.

   ------- Additional comments from andreas Thu Dec 11 08:00:19 -0700 2003 -------
There is a big overlap with issue #24.

   ------- Additional comments from sgrell Mon Dec 12 02:39:46 -0700 2005 -------
Changed subcomponent.

Stephan

Change History (0)

Note: See TracTickets for help on using tickets.