<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>I think someone asked this same exact question a few weeks ago.
The best solution I know of is to use Arbiter, which was created
exactly for this situation. It uses cgroups to limit resource
usage, but it adjusts those limits based on login node utilization
and each users behavior ("bad" users get their resources limited
more severely when they do "bad" things.<br>
</p>
<p>I will be deploying it myself very soon. <br>
</p>
<p><a href="https://dylngg.github.io/resources/arbiterTechPaper.pdf"
target="_blank">https://dylngg.github.io/resources/arbiterTechPaper.pdf</a></p>
<pre class="moz-signature" cols="72">Prentice</pre>
<div class="moz-cite-prefix">On 4/23/21 10:37 PM, Cristóbal Navarro
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CACg_LAX86DSOBMeFAs3MNBGHOXRLcR=e54e08uFQ5oJ+cgnjcw@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div>Hi Community,</div>
<div>I have a set of users still not so familiar with slurm, and
yesterday they bypassed srun/sbatch and just ran their CPU
program directly on the head/login node thinking it would
still run on the compute node. I am aware that I will need to
teach them some basic usage, but in the meanwhile, how have
you solved this type of user-behavior problem? Is there a
preffered way to restrict the master/login resources, or
actions, to the regular users ? <br>
</div>
<div><br>
</div>
many thanks in advance<br>
<div>-- <br>
<div dir="ltr" class="gmail_signature"
data-smartmail="gmail_signature">
<div dir="ltr">
<div>
<div dir="ltr">
<div>
<div dir="ltr">Cristóbal A. Navarro<br>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</body>
</html>