Thank you both for the information, and thanks for the prolog tip. I hadn't
thought of that.
__
*Jacob D. Chappell*
*Research Computing Associate*
Research Computing | Research Computing Infrastructure
Information Technology Services | University of
You can use slurmctl prologue to save it the way you want.
cheers,
Marcin
2017-11-30 0:25 GMT+01:00 Chris Samuel :
> On 30/11/17 8:57 am, Jacob Chappell wrote:
>
> Using "scontrol show jobid X" I can see info about running jobs, including
>> the command used to launch the job, the user's worki
On 30/11/17 8:57 am, Jacob Chappell wrote:
Using "scontrol show jobid X" I can see info about running jobs,
including the command used to launch the job, the user's working
directory, values of stdout, stdin, stderr, etc.
Note that the announcement for 17.11.0 mentions that the job script
wil
All,
Using "scontrol show jobid X" I can see info about running jobs, including
the command used to launch the job, the user's working directory, values of
stdout, stdin, stderr, etc. With Slurm accounting configured, sacct seems
to show *some* of this information about jobs that have completed. H
