Opened 11 years ago
Last modified 10 years ago
#753 new defect
IZ3203: qconf -aprj should accept project name
Reported by: | bovine | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | sge | Version: | 6.2u3 |
Severity: | Keywords: | clients | |
Cc: |
Description
[Imported from gridengine issuezilla http://gridengine.sunsource.net/issues/show_bug.cgi?id=3203]
Issue #: 3203 Platform: All Reporter: bovine (bovine) Component: gridengine OS: All Subcomponent: clients Version: 6.2u3 CC: [_] stephendennis [_] Remove selected CCs Status: NEW Priority: P3 Resolution: Issue type: DEFECT Target milestone: --- Assigned to: roland (roland) QA Contact: roland URL: * Summary: qconf -aprj should accept project name Status whiteboard: Attachments: Issue 3203 blocks: Votes for issue 3203: Opened: Tue Dec 1 17:47:00 -0700 2009 ------------------------ It seems that almost all of the object types that are creatable through qconf -axxx now allow the object name to be specified on the command-line and it will be used to pre-populate the template in the editor. One notable object that does not yet allow this is projects through the "qconf -aprj" option. Adding this functionality is a convenience to the admin, since typically the name is the only required field that needs to be specified. This would also simplify automation by allowing simple one-liners such as: env EDITOR=touch qconf -aprj moocow (This technique is already possible for most of the other object types today.)
Note: See
TracTickets for help on using
tickets.