On 10/31/22 5:46 am, Davide DelVento wrote:
Thanks for helping me find workarounds.
No worries!
My only other thought is that you might be able to use node features &
job constraints to communicate this without the user realising.
I am not sure I understand this approach.
I was just tryi
Thanks for helping me find workarounds.
> My only other thought is that you might be able to use node features &
> job constraints to communicate this without the user realising.
I am not sure I understand this approach.
> For instance you could declare the nodes where the software is installed
On 30/10/22 12:27 pm, Davide DelVento wrote:
But if I understand correctly your Prolog vs TaskProlog distinction,
the latter would have the environmental variable and run as user,
whereas the former runs as root and doesn't get the environment,
That's correct. My personal view is that injectin
Hi Chris,
> Unfortunately it looks like the license request information doesn't get
> propagated into any prologs from what I see from a scan of the
> documentation. :-(
Thanks. If I am reading you right, I did notice the same thing and in
fact that's why I wrote that job_submit lua script which
On 30/10/22 10:23 am, Chris Samuel wrote:
Unfortunately it looks like the license request information doesn't get
propagated into any prologs from what I see from a scan of the
documentation. 🙁
This _may_ be fixed in the next major Slurm release (February) if I'm
reading this right:
https:
On 29/10/22 7:37 am, Davide DelVento wrote:
So either I misinterpreted that "same environment as the user tasks"
or there is something else that I am doing wrong.
Slurm has a number of different prologs that can run which can cause
confusion, and I suspect that's what's happening here.
The
Thanks Jeff.
That's exactly the documentation that I looked and quoted, and yes, I
know that the user running the prolog is a different one (root) from
the one which will be running the job (regular user submitting the
job).
I speculated that the sentence I quoted (again: prolog is executed
with th
Not sure if this will help. It has which user will execute the scripts
https://slurm.schedmd.com/prolog_epilog.html
Maybe the variable isn't set for the user executing the prolog/epilog/taskprolog
Jeff
From: slurm-users on behalf of Davide
DelVento
Sent: Sat
