Hi Thomas,
you could think about using the USE_QSUB_GID execd_param. The user then
would have to switch to the desired group prior to submitting the job.
So something like 'newgrp storage_grp qsub ...'
That may cause other trouble, of course, e.g. when accessing the script
file during the submission itself. And if you use CSP mode then there
may be further implications.
Cheers,
Fritz
Thomas Finnern schrieb:
Hi there,
we need to control the primary group of a users job on our
exec hosts in order to organise e.g. storage access.
Currently we observe that a users processing environment
uses always his primary unix group. As our users work
for different projects it might happen, that even on
a single worker node two jobs of the same user should
run under different groups ...
Any ideas or hints are welcome ...
Regards, Thomas
PS:
Playing a around with an example:
user x has primary group ga and secondary group gb
We need to implement something like:
submit from host ha -> jobs executed with primary group ga, secondary
group gb
submit from host hb -> jobs executed with primary group gb, secondary
group ga
or alternatively via projects:
submit with project pa -> jobs executed with primary group ga,
secondary group gb
submit with project pb -> jobs executed with primary group gb,
secondary group ga
How can this be achieved?
_______________________________________________
users mailing list
[email protected]
https://gridengine.org/mailman/listinfo/users
--
 Fritz Ferstl | CTO and Business Development, EMEA
Univa
Corporation | The Data Center Optimization Company
E-Mail:
[email protected] | Phone: +49.9471.200.195 | Mobile:
+49.170.819.7390
|
_______________________________________________
users mailing list
[email protected]
https://gridengine.org/mailman/listinfo/users
