[torqueusers] process using more CPUs than requested

Christopher Samuel samuel at unimelb.edu.au
Wed Mar 2 17:33:46 MST 2011


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 19/02/11 11:05, Gus Correa wrote:

> I thought the Torque pam module (pam_pbssimpleauth.so)
> would prevent users to ssh to the nodes directly.

That's usually done to allow a user who has a job on the
node to ssh in (either to check on it, or for broken MPI
launchers which don't support the Torque TM interface -
yes Intel MPI, I'm looking at you..).

What I would really like to see is a re-architecture of
the cpuset support which would move to this model:

/dev/cpuset/torque/$user/$jobID

Then (SSH security model permitting) it would be nice
if pam_pbssimpleauth could move such logins into the
/dev/cpuset/torque/$user cpuset so at least they would
be contained in the superset of all that users jobs.

Hmm, actually pbs_mom could even spot user tasks not
in a cpuset and move them into them.. ;-)

cheers!
Chris
- -- 
    Christopher Samuel - Senior Systems Administrator
 VLSCI - Victorian Life Sciences Computation Initiative
 Email: samuel at unimelb.edu.au Phone: +61 (0)3 903 55545
         http://www.vlsci.unimelb.edu.au/

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk1u4eoACgkQO2KABBYQAh/fvwCfXJaLdjUqI/EFdh6mUUDejBZH
EJwAnj5ldlOxngI4ciIA0trZCnpM8KqY
=Wvr4
-----END PGP SIGNATURE-----


More information about the torqueusers mailing list