Opened 14 years ago
Last modified 10 years ago
#465 new enhancement
IZ2388: Job specifics including scripts should be archived for better administration/debugging/tracking.
Reported by: | andreas | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | sge | Version: | 6.1 |
Severity: | Keywords: | kernel | |
Cc: |
Description
[Imported from gridengine issuezilla http://gridengine.sunsource.net/issues/show_bug.cgi?id=2388]
Issue #: 2388 Platform: All Reporter: andreas (andreas) Component: gridengine OS: All Subcomponent: kernel Version: 6.1 CC: None defined Status: NEW Priority: P3 Resolution: Issue type: ENHANCEMENT Target milestone: --- Assigned to: andreas (andreas) QA Contact: andreas URL: * Summary: Job specifics including scripts should be archived for better administration/debugging/tracking. Status whiteboard: Attachments: Issue 2388 blocks: Votes for issue 2388: Opened: Thu Oct 4 03:49:00 -0700 2007 ------------------------ DESCRIPTION: The current behavior for Sun N1 Grid Engine with each submitted job is to store the job script in its spool system, then throw the job script away after the job has been executed. Also, there's no easy way for an administrator or a user to retrieve the full command line that was used for submitting the job after it has been submitted and more so after the job has been executed and put to rest. Actually, it is impossible to issue a qresub if the job has been completely executed because it's associated job script is no longer available.
Note: See
TracTickets for help on using
tickets.