Hello,On my login nodes I run a ulimit of -t 600 to keep users from running jobs on the login nodes. Previously with Torque/Moab, upon executing the job the shell session would spawn and read from my /etc/profiles where I had a script to read the hostname and set ulimits based on hostname.
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, although I haven't found a way to force this upon all submitted jobs. I've tried using /etc/sysconfig/slurm and it appears this file is ignored. I would even be happy if this is something that I could set in the job_submit.lua plugin, but I have not seen a variable for something like this.
Any ideas? ------------------- Nicholas McCollum HPC Systems Administrator Alabama Supercomputer Authority
smime.p7s
Description: S/MIME Cryptographic Signature
