But why... If your users would like to use idle compute servers - just tell them to start interactive jobs.
srun --pty /bin/bash They get the interactive use they want, you get to retain control using Slurm. Just think - what if you want to shut down a node for planned maintenance? With Slurm you use scontrol. In your scheme you would have to log into nodes and then warn the users to log out, then set an /etc/nologin Use the Batch System, Luke... Use the Batch System On 6 May 2017 at 19:56, Aurelien Bouteiller <[email protected]> wrote: > > Hi all, > > I’d like to have all my users being able to SSH to the compute nodes when > -nobody- has an active allocation on the node. I’d like to still use PAM > access control to prevent users logging into compute nodes that are > allocated through Slurm. > > I have made experiments with this and found easily how to make the pam > module prevent non-allocated users access. > However, users are also prevented to login at all time, even when no work > is active on a node. > > The typical workload for this machine is mostly debugging/shared jobs, > with (occasional) exclusive batch jobs. I can also appreciate advises on a > more Slurmy workflow for that type of usage pattern. > > Best, > Aurelien > -- > Aurélien Bouteiller, Ph.D. ~~ https://icl.cs.utk.edu/~bouteill/ >
