Sorry for the delay.
I have tried those parameters and while it does prevent propogation
of ulimits, it does not seem to work for srun or MPI jobs lauched with
srun inside an sbatch, therefor it seems any users that start jobs with
SRUN are limited to the ulimits of my login nodes.
After som
On 06/03/2016 08:28 PM, Nicholas McCollum wrote:
> Slurm uses a totally different process to execute the jobs, which is
> fine... except the jobs inherit the ulimits from my login nodes. I
> have found that this can be circumvented by using --propagate=NONE while
> submitting the sbatch command,
