On 29-04-2021 18:54, Ryan Novosielski wrote:
It may not for specifically PropagateResourceLimits – as I said, the docs are a
little sparse on the “how” this actually works – but you’re not correct that
PAM doesn’t come into play re: user jobs. If you have “UsePam = 1” set, and
have an /etc/pam
So I decided to eat my own dog food, and tested this out myself. First
of all, running ulimit through srun "naked" like that doesn't work,
since ulimit is a bash shell builtin, so I had to write a simple shell
script:
$ cat ulimit.sh
#!/bin/bash
ulimit -a
By default, core is set to zero in
What I said in my last e-mail (which you probably haven't gotten to yet)
is similar to this case. On it's own Slurm wouldn't propagate resource
limits, but that as been added as a function. In your case, Slurm has
functionality built into it where you can tell it to use PAM. With this
functiona
It may not for specifically PropagateResourceLimits – as I said, the docs are a
little sparse on the “how” this actually works – but you’re not correct that
PAM doesn’t come into play re: user jobs. If you have “UsePam = 1” set, and
have an /etc/pam.d/slurm, as our site does, there is some amoun
On 4/28/21 2:26 AM, Diego Zuccato wrote:
Il 27/04/2021 17:31, Prentice Bisbal ha scritto:
I don't think PAM comes into play here. Since Slurm is starting the
processes on the compute nodes as the user, etc., PAM is being bypassed.
Then maybe slurmd somehow goes throught the PAM stack another w
