[torqueusers] ulimit -l

Garrick Staples garrick at clusterresources.com
Wed Mar 28 15:57:47 MDT 2007


On Wed, Mar 28, 2007 at 01:45:20PM +0100, David Golden alleged:
> On Wednesday 28 March 2007 00:16, Brock Palen wrote:
> 
> > >
> > > Then the next thing is you have to restart the torque daemons on
> > > each system.  The reason for this is if they were started before
> > > you made these changes they hold the old limits and all processes
> > > they spawn will inherit those limits.  So restarting will get
> > > Torque going with the "unlimited" mode so child processes inherit
> > > that.
> > >
> 
> I find it safest to add explicit ulimit calls in the etc/init.d/torque_mom
> startup script or equivalent too - otherwise, because of the way the 
> pam_limits module works  (...at a login...), you can find that if you reboot 
> a node then the mom still autostarts with lower limits because init is 
> getting the system,er, default defaults, but then when you restart the mom 
> interactively, the mom gets the pam-set limits from root's login session and 
> appears to work fine (i.e. it gets large limits and its large limits get 
> inherited by its children...) -  confusing the first time it happens...

Indeed.  You actually want to do it in both places: pbs_mom's start up
script to effect the initial job script and any TM processes, and in pam
to effect remote rsh/ssh processes.



More information about the torqueusers mailing list