Ticket 10612 - expand new record fields "stdout/stderr" to sacct
Summary: expand new record fields "stdout/stderr" to sacct
Status: OPEN
Alias: None
Product: Slurm
Classification: Unclassified
Component: Accounting (show other tickets)
Version: 20.11.2
Hardware: Linux Linux
: C - Contributions
Assignee: Tim Wickberg
QA Contact:
URL:
: 18578 (view as ticket list)
Depends on:
Blocks:
 
Reported: 2021-01-11 19:26 MST by zhangtao102019@126.com
Modified: 2025-03-20 10:18 MDT (History)
2 users (show)

See Also:
Site: -Other-
Alineos Sites: ---
Atos/Eviden Sites: ---
Confidential Site: ---
Coreweave sites: ---
Cray Sites: ---
DS9 clusters: ---
HPCnow Sites: ---
HPE Sites: ---
IBM Sites: ---
NOAA SIte: ---
NoveTech Sites: ---
Nvidia HWinf-CS Sites: ---
OCF Sites: ---
Recursion Pharma Sites: ---
SFW Sites: ---
SNIC sites: ---
Tzag Elita Sites: ---
Linux Distro: ---
Machine Name:
CLE Version:
Version Fixed:
Target Release: ---
DevPrio: ---
Emory-Cloud Sites: ---

Attachments
Make sacct enable to print stdout/stderr path (18.92 KB, application/mbox)
2021-01-11 19:26 MST, zhangtao102019@126.com 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this ticket.
Description zhangtao102019@126.com 2021-01-11 19:26:45 MST 
Created attachment 17422 [details]
Make sacct enable to print stdout/stderr path

hi,

When i was in the operation and maintenance of slurm cluster, we need to get history job's  stdout/stderr path with sacct command.

Similar to previous bug 10611, i tried to add the "stdout/stderr" field for sacct. 

See the attachment for detail changes.
In my cluster environment, the patch works.

I'd like to confirm whether there are potential problems with this modification and whether it can be merged into the trunk.

Best Regards
Comment 1 Tim Wickberg 2024-01-04 12:22:54 MST 
*** Ticket 18578 has been marked as a duplicate of this ticket. ***