On 1/23/21 9:43 PM, Philip Kovacs wrote:
I can assure you it was easier for you to filter slurm from your repos
than it was for me to make them available to both epel7 and epel8.
No good deed goes unpunished I guess.
I do sympathize with your desire to make the Slurm installation a bit
easie
Thanks for the heads-up, Ole!
--
B/H
signature.asc
Description: PGP signature
I agree that by and large it’s no big deal, but a suggestion might be to
provide the SLURM as slurm-*- being the set of packages you install,
so that updating between major versions wouldn’t happen by surprise, given how
careful one needs to be with SLURM upgrades — ordering, timing, etc. Virtua
On Sat, 2021-01-23 at 20:43 +, Philip Kovacs wrote:
> I can assure you it was easier for you to filter slurm from your
> repos than it was for me to make them available to both epel7 and
> epel8.
Thanks for your efforts. Much appreciated.
--
Ian
Thanks Chris.
I think you have identified the issue here or are very close. My gres.conf on
the rtx-04 node for example is:
AutoDetect=nvml
Name=gpu Type=quadro_rtx_8000 File=/dev/nvidia0 Cores=0-15
Name=gpu Type=quadro_rtx_8000 File=/dev/nvidia1 Cores=0-15
Name=gpu Type=quadro_rtx_8000 File=/d
We also use the lmod system. We found that besides the user's shell, it
also depends on how you install it. I.e. need to be active for general
shell and not just for login shells (bashrc vs. profile). Also, for e.g.
/bin/sh, it might not read any init file at all.
As we might have different module
