Hi, everyone --
Our take on using epilog is likely familiar to many, but perhaps not all.
Here is an extract from epilog:
/usr/local/slurm/epilogctld:/usr/bin/scontrol show job=$SLURM_JOB_ID
--oneliner >> /usr/local/slurm/slurmrecord/$((SLURM_JOB_ID/1)).record
The file size may be adjusted. T
ilable via 'job accounting' and 'job completion'?
-- is the above (sketchy) summary consistent with the understanding of
experienced practitioners?
-- if relevant, which of the slurm documentation perhaps shed more light on
distinguishing between the 'accounting' and 'co
ecide to restrict the desktop app software to just a limited
number of nodes. I haven't yet thought of a way to prioritize availability
through setting a feature, since it's my perception that OnDemand is only
successful if requested resources become available with only a short delay
(~5 min or
b? And if so, what is going
on behind the scenes? I'd like to come away with better insight into how
the slurmdb operates. Pointers to slurmdb tutorials or slide decks are
welcome ;)
Best wishes, and thanks in advance
~ Em
--
E.M. Dragowsky, Ph.D.
Research Computing -- UTech
Case Western Reserve University
(216) 368-0082
ort squeue output:
[mrd20@hpc3 ~]$ squeue -o "%A %e %g %l %m %c %T %u %V" -S V
JOBID END_TIME GROUP TIME_LIMIT MIN_MEMORY MIN_CPUS STATE USER SUBMIT_TIME
squeue: error: Invalid sort specification: V
Why is submit time not allowed/supported as an argument to sort the output
of squeue?
