The ./configure --prefix=... value gets into the Makefiles, which is no
surprise. But it is also getting into the slurmd binary and .o files.
Here's what I found in the slurmd/ source directory:
$ find ./ -type f -exec grep
/home/dean/src/slurm.versions/slurm-19.05.4.build {} /dev/null \;
./Makef
I used a similar ./configure command:
./configure --prefix=/home/dean/src/slurm.versions/slurm-19.05.4.build
--sysconfdir=/etc/slurm --enable-pam
--with-pam_dir=/lib/x86_64-linux-gnu/security/ --without-shared-libslurm
--enable-debug
The problem is that the path in --prefix is getting into the sl
Hey Dean,
Here is what I found in my build notes which are now outdated by 1 year at
least, but probably there are some more configure parameters you want to
specify with relevant directories:
./configure --prefix=/tmp/slurm-build --sysconfdir=/etc/slurm --enable-pam
--with-pam_dir=/lib/x86_64-li
I built slurm on one machine (controller) and copied the new slurmd binary
to a node. When I started it systemctl it failed with the message:
fatal: Unable to find slurmstepd file at
/home/dean/src/slurm.versions/slurm-19.05.4.build/
The path it refers to is what I gave to ./configure --prefix==
Hi all,
I have a few more remarks about this question (I have been in contact with
Marcus about this):
- the idea of the jobscript is that SLURM does not do any binding and leaves
binding up to
mpirun.
- this works fine on the first node, where SLURM does not bind the
processes (so
