Robert Anderson writes:
> While working on an example python slurm job script I found the
> environment variable SLURM_ARRAY_TASK_MAX was not set to the expected
> value when a step is defined.
>
> Below is a minimal test of a 10 array job, with a step value of 5. When
> a step value is defined
Appears that the filetxt accounting just doesn't record those fields.
(The man page has a rather cryptic "Note: The filetxt plugin records only a
limited subset of accounting information and will prevent some sacct
options from proper operation."
I did not expect something like NCPUs to b
While working on an example python slurm job script I found the
environment variable SLURM_ARRAY_TASK_MAX was not set to the expected
value when a step is defined.
Below is a minimal test of a 10 array job, with a step value of 5. When
a step value is defined the SLURM_ARRAY_TASK_MAX is set to th
Hello,
Thanks for the link to the Linux Foundation blog post about ntp and Chrony.
I had been using ntp for years but will now switch to Chrony as its code
base is more modern, secure, and maintainable. Also hoping to just run less
code, and I like the sound of Chrony's simpler implementation.
As
