[Moabusers] MAXPROC enforcement order

[wightman at clusterresources.com]

Brock,

We found the issue.  It is the ',' in MAXPROC=1000,FSTARGET=15

The "official" delimiter for parameters in the moab.cfg file is white 
space.  In this case, Moab was trying to parse FSTARGET as the HARDLIMIT 
for MAXPROC.  Obviously that did notwork so it sets your MAXPROC HARDLIMIT 
to 0.  This results in your user picking up the DEFAULT MAXPROC of 32 :)

If you have seen anywhere in the documentation where ',' is used as a 
delimiter between moab.cfg parameters please let us know and we will fix 
it immediately.

So the easy fix is to change the ',' to ' '.

Let us know how this works for you.

Thanks,

- Douglas

On Wed, 21 Jun 2006, Brock Palen wrote: