Thanks for the suggestion Ole - I'll see if I can get that in the mix to try
over the next few days.
I can report that 23.02.7 tree had the same issues, so going backwards on the
slurm bits did not have any impact.
Brent
--
slurm-users mailing list -- slurm-users@lists.schedmd.com
To
{
"emoji": "",
"version": 1
}
--
slurm-users mailing list -- slurm-users@lists.schedmd.com
To unsubscribe send an email to slurm-users-le...@lists.schedmd.com
Hello. I am new to this list and Slurm overall. I have a lot of experience in
computer operations, including Kubernetes, but I am currently exploring Slurm
in some depth.
I have set up a small cluster and, in general, have gotten things working, but
when I try to run a container job, it runs
FYI, I submitted a bug about this in March because the "compatible" line in the
docs was confusing to me as well. The change coming to the docs removes that
altogether and simply says that setting it to OFF "disables job preemption and
gang scheduling". Much clearer.
And we do it the same
Someone may have said this already but you know that you can replace
0,5,10,15,20,25,30,35,40,45,50,55 with */5?
Tim
--
Tim Cutts
Scientific Computing Platform Lead
AstraZeneca
Find out more about R IT Data, Analytics & AI and how we can support you by
visiting our Service
I have integrated Podman with Slurm as per the docs (
https://slurm.schedmd.com/containers.html#podman-scrun) and when I do a
test run:
"podman run hello-world" (this runs fine)
$ podman run alpine hostname
executable file `/usr/bin/hostname` not found in $PATH: No such file or
directory
Sandor via slurm-users writes:
> I am working out the details of scrontab. My initial testing is giving me
> an unsolvable question
If you have an unsolvable problem, you don't have a problem, you have a
fact of life. :)
> Within scrontab editor I have the following example from the slurm
>
