Yes, the stuff in /etc/security/limits.d is only processed through pam sessions. Processes started through init do not go through pam.
Ben -----Original Message----- From: Trey Dockendorf <treyd...@tamu.edu> To: slurm-dev <slurm-dev@schedmd.com> Sent: Thu, 29 Jan 2015 23:43 Subject: [slurm-dev] Re: SLURM with VASP This is after I set "ulimit -s unlimited" in /etc/sysconfig/slurm. The job had -N4 --ntasks-per-node=4 and partition has MaxMemPerCPU=4000. core file size (blocks, -c) 0 data seg size (kbytes, -d) unlimited scheduling priority (-e) 0 file size (blocks, -f) unlimited pending signals (-i) 257745 max locked memory (kbytes, -l) unlimited max memory size (kbytes, -m) 15974400 open files (-n) 8192 pipe size (512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 real-time priority (-r) 0 stack size (kbytes, -s) unlimited cpu time (seconds, -t) unlimited max user processes (-u) 257745 virtual memory (kbytes, -v) 32108543 file locks (-x) unlimited The 'max locked memory' is set explicitly on compute nodes and the 'open files' is defined in /etc/sysconfig/slurm based on recommendation from docs. Thus far the unlimited stack size has allowed VASP to run long longer than it ever has previously using the input files I was given. It has even begun printing what I would assume is useful output (I know little of what to expect from VASP in terms of output). This is progress! Is there any reason to put that stack size of unlimited in /etc/sysconfig/slurm and not in /etc/security/limits.d/? I prefer the later as that's where I tend to look on a system when inspecting what limits are being set. Thanks, - Trey ============================= Trey Dockendorf Systems Analyst I Texas A&M University Academy for Advanced Telecommunications and Learning Technologies Phone: (979)458-2396 Email: treyd...@tamu.edu Jabber: treyd...@tamu.edu On Thu, Jan 29, 2015 at 4:15 PM, Christopher Samuel <sam...@unimelb.edu.au> wrote: > > On 30/01/15 07:19, Trey Dockendorf wrote: > > > I was not aware of that, thanks for teaching me something new. I'll add > > that ulimit to slurmd init script as one of my test cases for resolving > > this. > > Once you've done that can you send the output of "ulimit -a" from inside > the VASP batch job (just before it starts) so we can see what the limits > are please? > > thanks, > Chris > -- > Christopher Samuel Senior Systems Administrator > VLSCI - Victorian Life Sciences Computation Initiative > Email: sam...@unimelb.edu.au Phone: +61 (0)3 903 55545 > http://www.vlsci.org.au/ http://twitter.com/vlsci >
