Yes — I am running CentOS 7. So to be clear, PAM has no impact on solving this problem on CentOS/RHEL 7, and this is the only way to make sure things are right?
> On Jan 7, 2016, at 3:01 PM, Wiegand, Paul <[email protected]> wrote: > > Are you running systemd (e.g., CentOS 7 or RHEL 7)? If so, the ulimit > solution mentioned in the FAQ does not work. Instead, you need to put these > lines in the [] section of your service files: > > LimitMEMLOCK=infinity > LimitSTACK=infinity > LimitCPU=infinity > > Paul. > > >> On Jan 7, 2016, at 14:53, Novosielski, Ryan <[email protected]> wrote: >> >> I read this awhile ago and it was on my list of things to do to ask a >> clarifying question — does this mean that if I’m running SLURM with PAM, I’m >> good on this just automatically? Is there a smart way to check? Running a >> job that just does “ulimit -a” maybe? >> >>> On Jan 7, 2016, at 2:18 PM, [email protected] wrote: >>> >>> >>> See FAQ: >>> http://slurm.schedmd.com/faq.html#rlimit >>> >>> Quoting Michael Richard Colonno <[email protected]>: >> >> ____ *Note: UMDNJ is now Rutgers-Biomedical and Health Sciences* >> || \\UTGERS |---------------------*O*--------------------- >> ||_// Biomedical | Ryan Novosielski - Senior Technologist >> || \\ and Health | [email protected] - 973/972.0922 (2x0922) >> || \\ Sciences | OIRT/High Perf & Res Comp - MSB C630, Newark >> `' >> > ____ *Note: UMDNJ is now Rutgers-Biomedical and Health Sciences* || \\UTGERS |---------------------*O*--------------------- ||_// Biomedical | Ryan Novosielski - Senior Technologist || \\ and Health | [email protected] - 973/972.0922 (2x0922) || \\ Sciences | OIRT/High Perf & Res Comp - MSB C630, Newark `'
signature.asc
Description: Message signed with OpenPGP using GPGMail
