Opened 12 years ago
Last modified 4 years ago
#576 new feature
IZ2739: No way to remove a -notify flag, once it was set
Reported by: | reuti | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | sge | Version: | 6.1u5 |
Severity: | blocker | Keywords: | clients |
Cc: |
Description
[Imported from gridengine issuezilla http://gridengine.sunsource.net/issues/show_bug.cgi?id=2739]
Issue #: 2739 Platform: All Reporter: reuti (reuti) Component: gridengine OS: All Subcomponent: clients Version: 6.1u5 CC: None defined Status: NEW Priority: P3 Resolution: Issue type: FEATURE Target milestone: --- Assigned to: roland (roland) QA Contact: roland URL: * Summary: No way to remove a -notify flag, once it was set Status whiteboard: Attachments: Issue 2739 blocks: Votes for issue 2739: Opened: Sat Sep 27 13:24:00 -0700 2008 ------------------------ When -notify was set, it can't be removed later on with qalter (only within qmon you have this option). - an additonal argument to -notify (which might break existing scripts) - a new argument -warn y[es]|n[o] and call -notify deprecated - an additional option -unnotify or -nonotify
Change History (1)
comment:1 Changed 4 years ago by nicoulaj
- Keywords removed
- Severity set to blocker
Note: See
TracTickets for help on using
tickets.
This feature would be useful in the following use case:
=> Then there is no way to override the settings and force kill jobs immediately (with KILL signal).
Related mailing thread: http://gridengine.org/pipermail/users/2017-March/009605.html