On 21/03/18 19:09, Daniel Grimwood wrote:
Hi Chris,
Hiya!
Thanks for that. I had overlooked SBATCH_EXPORT as I interpreted the
man page literally, as "Same as --export". It's actually "Same as
--export without setting SLURM_EXPORT_ENV=NONE". That's great!
My pleasure. :-)
Now all we n
Hi Chris,
Thanks for that. I had overlooked SBATCH_EXPORT as I interpreted the man
page literally, as "Same as --export". It's actually "Same as --export
without setting SLURM_EXPORT_ENV=NONE". That's great!
Now all we need for completeness is a SRUN_EXPORT that works the same,
although SBATCH
Hi Daniel,
On Wednesday, 21 March 2018 4:05:59 PM AEDT Daniel Grimwood wrote:
> What do others do to work with SLURM_EXPORT_ENV, or am I missing something?
On OzStar we set this in the users environment for everyone:
SBATCH_EXPORT=none
The nice thing there is that because it's set beforehand s
Hi,
Due to some users submitting jobs across clusters, and because a clean
environment is easier to reproduce and debug, we ask all our users to add:
#SBATCH --export=NONE
in every jobscript.
The downside to this is that sbatch sets SLURM_EXPORT_ENV, which srun uses
and then exports no no
