A wrapper script that takes what is to be executed, check it out and
then dplace it to a certain CPU(s) comes to mind. Since dplace can also
maintain a global count of all active tasks in each CPU that should not
be a problem for you to check out what happens at your end.
If it's not going to be a wrapper script, then that could form part of
your queue system scripts. We handle this issue by placing the dplace
arguments in our PBS scripts.
Maybe someone has a more straightforward solution, but this is what we do.
--
--
George B. Magklaras
Senior Computer Systems Engineer/UNIX Systems Administrator
The Biotechnology Centre of Oslo,
University of Oslo
http://www.biotek.uio.no/
EMBnet Norway: http://www.biotek.uio.no/EMBNET/
Mark Haney wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I have an SGI box that I want to be able to allow certain users access
only to certain processors. I looked at dplace and cpuset, but they
both rather require the user to manage the jobs. As this is less than
perfect, is there a way to limit a user to be able to run jobs on only
certain CPUs, similar to sudo where a user my be able to have root
access to certain applications?
- --
Interdum feror cupidine partium magnarum Europae vincendarum
Mark Haney
Sr. Systems Administrator
ERC Broadband
(828) 350-2415
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFEX3OUYQhnfRtc0AIRAnFyAKC8i3Gmx17V4/Z8/qhjYPmQFKBozgCgj9/f
TsL0Xd3DZigDgQmUWbYatvY=
=JQ7f
-----END PGP SIGNATURE-----
--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list
