Thanks! Disabling pam_systemd.so fixed it. Ole's wiki also mentioned that,
but I didn't see pam_systemd.so at first. It was in common-session rather
than common-account. All is good now!
On Sun, Sep 24, 2017 at 8:23 AM, TO_Webmaster wrote:
>
> You might have to disable
On 21/09/17 00:29, Jacob Chappell wrote:
> I still have one weird issue. I'm probably missing another setting
> somewhere. The cgroup that the SSH session is adopted into does not seem
> to include the /dev files.
That's something I can't help with I'm afraid, we're still on RHEL6.
In a job
My Wiki page summarizes what's known about the pam_slurm_adopt setup.
May I remind you of my previous answer:
There is now a better understanding of how to use slurm-pam_slurm with Slurm
17.02.2 or later for limiting SSH access to nodes, see:
https://bugs.schedmd.com/show_bug.cgi?id=4098
I did not have that option set, thanks :) The SSH session is indeed being
adopted by the running job now (I can login and view this in the
authentication logs). Sorry for all of the questions and hassle, but, I
still have one weird issue. I'm probably missing another setting somewhere.
The cgroup
On 20/09/17 06:39, Jacob Chappell wrote:
> Thanks everyone who has replied. I am trying to get pam_slurm_adopt.so
> implemented. Does it work with batch jobs?
It does indeed, we use it as well.
Do you have:
PrologFlags=contain
set? From slurm.conf:
Contain At job allocation time, use
Thanks everyone who has replied. I am trying to get pam_slurm_adopt.so
implemented. Does it work with batch jobs? I keep getting errors, even
though I have a job running on the node I'm trying to login to:
jacob@condo:~$ sbatch nvidia-docker-test.sh
Submitted batch job 41
jacob@condo:~$ squeue
> On 9/19/17, 11:49 AM, "Trafford, Tyler" wrote:
>
>>Have you looked at "pam_slurm_adopt.so"?
>>
>>We are using that successfully. It "adopts" the cgroup of the user's job.
>
> We also use pam_slurm_adopt.so, and I¹m mostly happy with it. One caution
> is that the doco
> I found an old mailing list discussion about this. I'm curious if any
> progress has been made since and if there is a solution now?
>
> Is there a way to limit the SSH sessions of users to the cgroup defined by
> their jobs? I'm using pam_slurm.so to limit SSH access
> to only those users
>> Is there a way to limit the SSH sessions of users to the cgroup defined by
>> their jobs? I'm using pam_slurm.so to limit SSH access to only those users
>> with running jobs. However, if a user reserves say 2 GPUs on a 4 GPU system,
>> the cgroups only give their job access to 2 GPUs. But,
On 09/19/2017 03:25 PM, Jacob Chappell wrote:
I found an old mailing list discussion about this. I'm curious if any
progress has been made since and if there is a solution now?
There is now a better understanding of how to use slurm-pam_slurm with
Slurm 17.02.2 or later for limiting SSH
10 matches
Mail list logo