> Naively, you could always add an echo $var > somefile to your sbatch and
> review the output after the job started, to verify that $var is set
> correctly.
>
> Usualy, one can use --export or --get-user-env switches in sbatch to
> force environment propagation to jobs.
>
Thanks for your reply!
In the case in which I need it, though, it is not for debugging - I would like
(as slurm administrator) to access the environment of already submitted
(running, pending) jobs from *all* users
to check whether all our users have set a special environment variable. Then I
could notify those who forgot / failed to do that.
Since the slurm controller for sure stores the environment for the job to ship
it to the slurmstepd's once the jobs start execution, I assumed it would be
easy to just query the environment with scontrol / sstat, but it seems that's
not (yet?) possible...
Can I maybe find it in the state-files the slurm-controller stores on the
filesystem? If so, where I should I look?
Cheers,
Oliver
