Opened 15 years ago
Closed 8 years ago
#379 closed enhancement (fixed)
IZ2102: Interpret $TASK_ID also for non-array jobs in -o / -e
Reported by: | reuti | Owned by: | Dave Love <d.love@…> |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | sge | Version: | 6.0u8 |
Severity: | Keywords: | kernel | |
Cc: |
Description
[Imported from gridengine issuezilla http://gridengine.sunsource.net/issues/show_bug.cgi?id=2102]
Issue #: 2102 Platform: All Reporter: reuti (reuti) Component: gridengine OS: All Subcomponent: kernel Version: 6.0u8 CC: None defined Status: NEW Priority: P3 Resolution: Issue type: ENHANCEMENT Target milestone: --- Assigned to: andreas (andreas) QA Contact: andreas URL: * Summary: Interpret $TASK_ID also for non-array jobs in -o / -e Status whiteboard: Attachments: Issue 2102 blocks: Votes for issue 2102: Opened: Tue Sep 26 02:45:00 -0700 2006 ------------------------ Some automatic processing would be easier to implement, if also non-array jobs would have a task id set in their filenames (-o / -e), which could be 0. The assembly of the filenames seems to happen in "execd/get_path.c": if (ja_task_id) { if (!strncmp(t, "$TASK_ID", sizeof("$TASK_ID") - 1)) { sprintf(exp_path, "%s" sge_u32, exp_path, ja_task_id); s = t + sizeof("$TASK_ID") - 1; } } by removing the ja_task_id test and use just the 0. So the RFE would be to interpret $TASK_ID always in -o / -e. Maybe keeping the default name without an additional .0 at the end, would allow users to decide whether non-array jobs should have such an extension or not. If they want it, the simply have to request: -o '$JOB_NAME.o$JOB_ID.$TASK_ID' (well, the po/pe output will be joint with o/e this way, which you can't prevent).
Change History (1)
comment:1 Changed 8 years ago by Dave Love <d.love@…>
- Owner set to Dave Love <d.love@…>
- Resolution set to fixed
- Status changed from new to closed
Note: See
TracTickets for help on using
tickets.
In 4493/sge: