My mistake - I hadn't noticed that I was on the moab page instead of the maui page. The equivalent maui page doesn't list NMATCHPOLICY as one of the supported job extensions so you're probably right - I don't think that parameter is implemented in maui. I'll try one of the approaches you're suggesting. Thanks.
On Feb 9, 2011, at 14:17, Roy Dragseth wrote: > On Wednesday, February 09, 2011 21:55:38 Vicker, Darby (JSC-EG311) wrote: > > A little more information - to see if this was a general maui problem or > > just an issue with the torque/maui handoff, I set "JOBNODEMATCHPOLICY > > EXACTPROC" in maui.cfg. In this case "checkjob -v" reports the ppn=16 > > nodes as "rejected : CPU" as expected. So it appears to be a problem with > > communicating the information correctly between torque and maui and not > > the JOBNODEMATCHPOLICY parameter itself. According to the documentation > > here: > > > > http://www.adaptivecomputing.com/resources/docs/mwm/13.3rmextensions.php > > If you look at this page it says MOAB on the top, not maui. So I'm guessing > this isn't implemented in maui. You can achieve the same thing in > maui/torque > with queues or node properties if you don't like the -Wx=.... syntax. > > Queues: > > 1. the default queue can run jobs on all nodes > 2. the eightcore queue only access the 8core nodes > 3. the sixteencore queue only access the 16core nodes > > qsub -l.... -qeightcore ........ > > Node properties: > > give 8core and 16core properties to the relevant nodes > > qsub -lnodes=8:ppn=8:8core .......... > > r. _______________________________________________ mauiusers mailing list [email protected] http://www.supercluster.org/mailman/listinfo/mauiusers
