I have what you request setup in my environment. Preemption is the only
way to go. And you don't want to suspend the pre-empted jobs - you want
to requeue them. If you suspend them, the just stop executing but still
stay in memory, so the amount of memory needed by the preempting job may
not be
I have this same problem - a user writes to me about a problem they're
having with Slurm, and instead of pasting the script into the support
ticket or e-mail, give me the path to it. When finally get to looking at
it, it's obviously they've changed it since reporting the issue, so I
have no for
Which fields are you talking about. All of the fields seem to be
well-documented in the sacct man page
(https://slurm.schedmd.com/sacct.html). For example, you mention the
time fields. For format for all the time fields seem to be rather well
documented (See below) and you can use the SLURM_TIM
On Fri, 5 Mar 2021 at 7:51am, Kilian Cavalotti wrote
Hi Joshua,
On Thu, Mar 4, 2021 at 8:38 PM Joshua Baker-LePain wrote:
slurmd: error: _nvml_get_mem_freqs: Failed to get supported memory frequencies
slurmd: error: for the GPU : Not Supported
slurmd: 4 GPU system device(s) detected
slu
Hi Joshua,
On Thu, Mar 4, 2021 at 8:38 PM Joshua Baker-LePain wrote:
> slurmd: error: _nvml_get_mem_freqs: Failed to get supported memory
> frequencies
> slurmd: error: for the GPU : Not Supported
> slurmd: 4 GPU system device(s) detected
> slurmd: WARNING: The following autodetected GPUs a
Hi all,
Sorry if this has been ask and answered before.
Resulting from a user/owner requirement I would need to set-up a subset of a
nodes in a partition be used as common shared resources still, but these nodes
should be available with smallest latency possible in case the owner wants run
a
I put this line in my job-control file (written in bash) to capture the
original as part of the run:
cp $0 $RUNDIR/$SLURM_JOB_NAME
The $0 gives the full path to the working copy of the script, so it
expands to this for example:
/fs/slurm/var/spool/job67842/slurm_script
It depends on t
Hi,
On 5/03/2021 11:29, Alberto Morillas, Angelines wrote:
> I know that when I send a job with scontroI can get the path and the
> name of the script used to send this job, but normally the users change
> theirs scripts and sometimes all was wrong after that, so is there any
> possibility to rep
Thanks!
De: slurm-users en nombre de
slurm-users-requ...@lists.schedmd.com
Enviado: Friday, March 5, 2021 1:00:01 PM
Para: slurm-users@lists.schedmd.com
Asunto: slurm-users Digest, Vol 41, Issue 13
Send slurm-users mailing list submissions to
slurm-use
On 05-03-2021 11:29, Alberto Morillas, Angelines wrote:
I would like to know if it will be possible to get the script that was
used to send a job.
I know that when I send a job with scontroI can get the path and the
name of the script used to send this job, but normally the users change
their
Hi,
I would like to know if it will be possible to get the script that was used to
send a job.
I know that when I send a job with scontroI can get the path and the name of
the script used to send this job, but normally the users change theirs scripts
and sometimes all was wrong after that, so i
Hi, Marcus,
Very grateful for you reply! I will try it out just as you suggested.
Best Regards,
Xiaojing
> On Mar 5, 2021, at 3:59 PM, Marcus Boden wrote:
>
> Hi Xiaojing,
>
> my experience here is: you will have to try it out and see what works. At
> least that's what I do whenever I parse
Hi Xiaojing,
my experience here is: you will have to try it out and see what works.
At least that's what I do whenever I parse sacct, as I did not find a
detailed description anywhere. The manpage is quite incomplete in that
regard.
Best,
Marcus
On 05.03.21 03:02, xiaojingh...@163.com wrote
13 matches
Mail list logo
