And also using cgroups; https://slurm.schedmd.com/cgroup.conf.html
Best wishes,
Rajiv
On 02/11/17 04:37, Christopher Samuel wrote:
On 02/11/17 14:34, 马银萍 wrote:
It means that he used only one cpu and asked for 125G memoey, so he used
most of the memory on that node, then it will affect othe
On Thursday, 2 November 2017 8:02:47 PM AEDT Rajiv Nishtala wrote:
> And also using cgroups; https://slurm.schedmd.com/cgroup.conf.html
That will constrain the memory a job can use to what it has asked for, but I
think that the original poster was asking how to stop a user asking for that
much
It can also constrain the memory a CPU can use. for instance, using
--mem-per-cpu ..I maybe wrong.
Best,
Rajiv
On 02/11/17 11:36, Chris Samuel wrote:
On Thursday, 2 November 2017 8:02:47 PM AEDT Rajiv Nishtala wrote:
And also using cgroups; https://slurm.schedmd.com/cgroup.conf.html
That
How does one go about disabling the Prolog and Epilog settings to mitigate
against the insecure SPANK environment variable handling issue referenced here:
https://www.schedmd.com/news.php?id=193#OPT_193
and here:
http://www.cvedetails.com/cve/CVE-2017-15566/
Is this done by just ensuring that “Pr
If a user has a program that is strictly single threaded but does need the
full (or close to) full amount of memory available should you be preventing
them from running?
I guess an argument can be made that this will encourage them to figure out
how to re-do their program multi-threaded but this ma
Thanks all for your repliy,
But what I need is to stop user to use --mem and --mem-per-cpu , but I
can't figure out this with cgroup and tres. How can I use the "submit
filter", should I modify the source code of SLURM?
Is there any way to config some files of SLURM to solve this problem?
All the b
