My understand from talking with the Slurm devs is that the reason why
the scontrol and sacct are different formats goes back to the origins of
those two commands in the misty past. Basically they were written by two
different devs looking at two different things in different ways as one
is querying the scheduler directly while the other is querying the
database. I have asked if command options and outputs could be unified
but the devs are worried about breaking existing scripts that rely on
the current formatting.
Suffice it to say the differences will likely never be resolved with out
everyone accepting that their existing tools will break in favor of
unifying all the command structures.
-Paul Edmon-
On 6/17/2025 7:42 AM, Davide DelVento via slurm-users wrote:
Yeah, that's an annoying thing which I have not understood why has
been designed that way. The information is there and it can be
queried, just with a different command and spitting it out in a
different format. The syntax is
sacct -j XXX
which gives you only some fields, or
sacct -o fields,you,want -j XXX
the (super long) list of possible fields (case insensitive) can be
queried with
sacct -e
HTH
On Tue, Jun 17, 2025 at 4:45 AM Gestió Servidors via slurm-users
<slurm-users@lists.schedmd.com> wrote:
Hello,
Is there any way to get all information (like submit script or
submit node) from a job that is completed? Something like
“scontrol show jobid=XXX” when job is “running” or “pending”. I
need to inspect the submit script of a job but I only know job_id.
Thanks.
--
slurm-users mailing list -- slurm-users@lists.schedmd.com
To unsubscribe send an email to slurm-users-le...@lists.schedmd.com
--
slurm-users mailing list -- slurm-users@lists.schedmd.com
To unsubscribe send an email to slurm-users-le...@lists.schedmd.com
