Sorry, one last time: Now the same issue is occuring with the package
slurmd.
What is going on here?
On Thu, Jul 10, 2025 at 5:09 PM Jesse Hayward wrote:
> Update: Definitely an apt problem, not a slurm one, apologies. Still
> ancient issues from an old gnome-control-center install a prior admi
Update: Definitely an apt problem, not a slurm one, apologies. Still
ancient issues from an old gnome-control-center install a prior admin did
years ago. Sheesh. Did many apt rebuilds and it never complained. Dpkg
rebuild + reboot solved the issue. Held packaged.
Glad we're moving to Rocky for ou
Hi all,
Unfortunately still struggling. I am not installing x11 on my compute
nodes. Especially not anything Ubuntu has to offer. See attached screenshot.
[image: 966c96eb-79c4-4f12-ba23-bf099bb9b1c6.png]
Best,
Jesse
On Tue, Jul 1, 2025 at 4:55 PM Jesse Hayward wrote:
> Thanks, all!
>
> Your a
I have defined DefCpuPerGPU for a partition but when a job specifies
--ntasks-per-gpu then DefCpuPerGPU is ignored and I only get 1 cpu:
```
#SBATCH --gpus=1
#SBATCH --ntasks-per-gpu=1
```
Is this the expected behaviour? The man page for DefCpuPerGPU says: "This
value is used only if the job didn
