#SBATCH --export=NONE solve my problem, thanks.
-Original Message-
From: Dr. Thomas Orgis [mailto:thomas.or...@uni-hamburg.de]
Sent: Friday, September 15, 2017 3:11 PM
To: slurm-dev
Subject: [slurm-dev] Re: why the env is the env of submit node, not the env of
job running node.
Hi
On 15 September 2017 at 17:09, Dr. Thomas Orgis wrote:
> Hi Zhang,
>
> the default behaviour of slurm is to try to keep the environment
> variables from the submit node. I do not like that and in our
> installation, we urge users to always specify
>
> #SBATCH --export=NONE
>
> to avoid that (or o
Hi Zhang,
the default behaviour of slurm is to try to keep the environment
variables from the submit node. I do not like that and in our
installation, we urge users to always specify
#SBATCH --export=NONE
to avoid that (or only specify a set of variables they want to pass to
the job) and then us
env?
>
>
>
> Thanks.
>
> *From:* Lachlan Musicman [mailto:data...@gmail.com]
> *Sent:* Friday, September 15, 2017 6:55 AM
> *To:* slurm-dev
> *Subject:* [slurm-dev] Re: why the env is the env of submit node, not the
> env of job running node.
>
>
>
> On
reasonable from my view.
Whether there is a way to configure slurm to use running node env, not submit
node env?
Thanks.
From: Lachlan Musicman [mailto:data...@gmail.com]
Sent: Friday, September 15, 2017 6:55 AM
To: slurm-dev
Subject: [slurm-dev] Re: why the env is the env of submit node, not the env
On 14 September 2017 at 19:41, Chaofeng Zhang wrote:
> On node A, I submit job file using sbatch command, the job is running on
> the node B, you will find that the output is not the env of node B, it is
> the env of node A.
>
>
>
> *#!/bin/bash*
>
> *#SBATCH --job-name=mnist10*
>
> *#SBATCH --pa
