Hi, I wonder where does this problems come from, perhaps I am missing something, but we never had such issues with limits since we have it set on worker nodes in /etc/security/limits.d/99-cluster.conf:
``` * soft memlock 4086160 #Allow more Memory Locks for MPI * hard memlock 4086160 #Allow more Memory Locks for MPI * soft nofile 1048576 #Increase the Number of File Descriptors * hard nofile 1048576 #Increase the Number of File Descriptors * soft stack unlimited #Set soft to hard limit * soft core 4194304 #Allow Core Files ``` and it sets up all limits we want without any problems, and there is no need to pass extra arguments to slurm commands or modify the config file. Regards, Patryk. On 24/05/15 02:26, Dj Merrill via slurm-users wrote: [-- Type: text/plain; charset=US-ASCII, Encoding: 7bit, Size: 0,2K --] > I completely missed that, thank you! > > -Dj > > > Laura Hild via slurm-users wrote: > > PropagateResourceLimitsExcept won't do it? > Sarlo, Jeffrey S wrote: > > You might look at the PropagateResourceLimits and > > PropagateResourceLimitsExcept settings in slurm.conf [-- Alternative Type #1: text/html; charset=UTF-8, Encoding: 8bit, Size: 1,0K --] > > -- > slurm-users mailing list -- slurm-users@lists.schedmd.com > To unsubscribe send an email to slurm-users-le...@lists.schedmd.com
smime.p7s
Description: S/MIME cryptographic signature
-- slurm-users mailing list -- slurm-users@lists.schedmd.com To unsubscribe send an email to slurm-users-le...@lists.schedmd.com
