On RedHat-based distributions, there were packages that would not be produced 
if the required libraries/headers were not available. So you will possibly need 
a package to be installed on the host where you are building this SLURM 
packages that is called something like some libpam-dev — I don’t quite remember 
the naming convention on Debian-based systems. I think the build process might 
work the same way though: don’t build what can’t be built/is missing 
dependencies.

You might also be able to install the required build dependencies by finding 
out what the currently installed PAM package is and doing apt build-dep 
<whatever name>.

Sorry, I’m not near a computer right now, but this might help you search for 
info.

--
____
|| \\UTGERS,       |---------------------------*O*---------------------------
||_// the State     |         Ryan Novosielski - 
novos...@rutgers.edu<mailto:novos...@rutgers.edu>
|| \\ University | Sr. Technologist - 973/972.0922 (2x0922) ~*~ RBHS Campus
||  \\    of NJ     | Office of Advanced Research Computing - MSB C630, Newark
    `'

On May 3, 2018, at 23:11, Will Dennis 
<wden...@nec-labs.com<mailto:wden...@nec-labs.com>> wrote:

Hello everyone,

Back a year ago or so, I started a new SLURM cluster, and had produced a .deb 
file from the then-current release archive (v16.05.4) that I compiled on a 
U16.04 host. I have successfully used that .deb which I included in our local 
custom repo to roll out the compute nodes of my cluster (which also run U16.04 
of course.) For what we have tried to do with it, it all appears to work well.

Now I am attempting to restrict users from logging into the compute nodes via 
the “pam_slurm” module as described at 
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fraw.githubusercontent.com%2FSchedMD%2Fslurm%2F5505db3a5076bfc301dba16e83fbc133e833cbd4%2Fcontribs%2Fpam%2FREADME&data=02%7C01%7Cnovosirj%40rutgers.edu%7C0f2b9d6ce25a4321f77308d5b16ca949%7Cb92d2b234d35447093ff69aca6632ffe%7C1%7C1%7C636610002641525065&sdata=msw8rVRFJGDPFAW2ip7LZpMw8IelEUMAjAqkscb81CE%3D&reserved=0.
 I put the following lines in the /etc/pam.d/sshd file at the bottom:

account    sufficient   pam_succeed_if.so user ingroup SYSOPS
account    required     pam_slurm.so

Unfortunately, I got a report that my users can not log into the compute nodes 
even when they have a job scheduled on the node. I came to find out that 
although I have many .so files from my .deb package all in 
/usr/lib/x86_64-linux-gnu/slurm, pam_slurm.so is not one of them... My question 
is, where could I acquire the proper pam_slurm.so shared lib file for U16.04, 
or, otherwise, how to compile it?

Thanks,

Will Dennis
Sr. Systems Administrator,
NEC Laboratories America

Reply via email to