Hello,
I would like to know if there is any mechanism to avoid a user to do "cheating"
when he submits a job. For example, a user submits a OpenMP job requesting 1
node (-N 1) and 2 tasks (-n 2). However, inside his script (or compiled in his
binany), user uses more than 2 ntasks, for example,
> When I run something like `srun -n 10 echo HELLO', I get HELLO
> returned to my console/stdout 10x. When I submit this command
> as a script to the /jobs/submit route, I get success/200, but I
> cannot determine how to get the console output of HELLO 10x in
> any form. It's not in my stdout log
If you submit the command as a script, the output and the error stream end
up in files, because you may logout, or have gazillion of other things or
other reasons, and therefore the stream to tty/console does not make sense
anymore
On Mon, Mar 24, 2025 at 8:29 AM Dan Healy via slurm-users <
slurm-
Hi Slurm Community,
I'm starting to experiment with slurmrestd for a new app we're writing. I'm
having trouble understanding one aspect of submitting jobs.
When I run something like `srun -n 10 echo HELLO', I get HELLO returned to
my console/stdout 10x.
When I submit this command as a script to t
Hi Slurm Users,
I have a newer install (23.11.3) and the priority of most all jobs is 1 and
other small numbers. In previous versions, I would see numbers like 2^32. I
have the multifactor plugin configured and confirmed it's in-use when I
show the config.
When I run `scontrol top` for a given jo
