On Tue, Jul 10, 2018 at 10:05 AM, Jessica Nettelblad
wrote:
> In the master branch, scontrol write batch_script also has the option to
> write the job script to STDOUT instead of a file. This is what we use in the
> prolog when we gather information for later (possible) troubleshooting. So I
> sup
Thank you very much. I can see it.
Regards,
Mahmood
On Tue, Jul 10, 2018 at 9:35 PM, Jessica Nettelblad <
jessica.nettelb...@gmail.com> wrote:
> Since 17.11, there's a command to write the job script to a file:
> "scontrol write batch_script job_id optional_filename
> Write the batch script fo
Since 17.11, there's a command to write the job script to a file:
"scontrol write batch_script job_id optional_filename
Write the batch script for a given job_id to a file. The file will default
to slurm-.sh if the optional filename argument is not given. The
batch script can only be retrieved by a
As in the submit script?
I believe "scontrol show jobid -dd $JOBID" (with $JOBID being the ID of the
job you're after) should show you. (Does for me anyway :) ).
Tina
On Tuesday, 10 July 2018 20:32:33 BST Mahmood Naderan wrote:
> Hi
> How can I check the submitted script of a running based on
scontrol show job -dd JOBID
then search
Command=
Best,
Shenglong
> On Jul 10, 2018, at 12:02 PM, Mahmood Naderan wrote:
>
> Hi
> How can I check the submitted script of a running based on its jobid?
>
>
> Regards,
> Mahmood
>
>
rom: slurm-users on behalf of Mahmood
Naderan
Sent: Tuesday, July 10, 2018 9:02:33 AM
To: Slurm User Community List
Subject: [slurm-users] Finding submitted job script
Hi
How can I check the submitted script of a running based on its jobid?
Regards,
Mahmood
Hi
How can I check the submitted script of a running based on its jobid?
Regards,
Mahmood
