[torquedev] Ommiting core 0 from /dev/cpuset/torque/cpus breaks cpusets

[Chris Samuel]

Hi folks,

It looks like if you pre-create /dev/cpuset/torque with
cores 1-n to cope with your system allocating core 0 for
a boot cpuset the current code doesn't cope and the jobs
end up with no cpus allocated to the job cpuset.

I've verified this with my current build but not had a
chance to check with trunk yet.

This was pointed out to me by Brian O'Conner from SGI
who's having problems posting to the list.

cheers,
Chris
-- 
Christopher Samuel - (03) 9925 4751 - Systems Manager
 The Victorian Partnership for Advanced Computing
 P.O. Box 201, Carlton South, VIC 3053, Australia
VPAC is a not-for-profit Registered Research Agency