On 2020/05/21 12:14, Christopher Samuel wrote:
On 5/20/20 7:23 pm, Kevin Buckley wrote:
Are they set as part of the job payload creation, and so would ignore
and node local lookup, or set as the job gets allocated to the various
nodes it will run on?
Looking at git, it's a bit of both:
src/slurmd/slurmd/req.c:
setenvf(&env, "SLURM_JOB_UID", "%u", job_env->uid);
[...]
setenvf(&env, "SLURM_JOB_USER", "%s", job_env->user_name);
so the variables get set on the slurmd side (as you'd expect) but from
data that is sent along with the job.
All the best,
Chris
That's good to know, Chris, thanks: especially at this late hour.
We've been seeing jobs start that sometimes don't resolve a $USER reference,
inside the job submission script, however, if the scripts use $SLURM_JOB_USER,
then they will get the value they need to procede.
The failure to resolve $USER has been seen to be transient, so that's another
issue in itself.
Cheers again, and a "good afternnon" from here.
Kevin
--
Supercomputing Systems Administrator
Pawsey Supercomputing Centre
