Hi,

> Am 14.09.2015 um 16:54 schrieb Daniel Gruber <dgru...@univa.com>:
> 
> Hi Joe,
> 
> Univa Grid Engine 8.3 added such a functionality to its APIs (WebService API)
> so that you can submit on behalf of another user. The intention is to
> simplify building web portals. But this is restricted to users listed in the 
> new sudoers Grid Engine ACL.

I always wondered about the -U flag in the accounting records which pops up 
here and there containing ACLs since a long time.


> We can chat privately about that if you like.
> 
> Daniel
> 
> 
>> Am 14.09.2015 um 16:27 schrieb Joe Borġ <m...@jdborg.com>:
>> 
>> Hi all,
>> 
>> I have a need to submit from a process that run by a single user.  When it 
>> comes to submit jobs, it is aware of a user that the job can run as.  Seeing 
>> as the shepherd and execd are run as root (therefore must be changing the 
>> user anyway), is there a way to override the user that the job will run as.  
>> I guess this would only be for people with manager permissions.
>> 
>> Currently, this is achieved with 
>> 
>> `sudo runuser -u user 'qsub ...'`

Isn't `sudo runuser ...` tautologous and one sufficient?


Is it always the same target user? It can be set up in /etc/sudoers that `sudo 
qsub ...` will automatically use the designated account:

Cmnd_Alias QSUB = /usr/sge/bin/lx24-amd64/qsub
Defaults!QSUB runas_default=soft, always_set_home, mail_always, mailto=reuti
%operator erwin = (soft) NOPASSWD: QSUB

$ sudo qsub test.sh

will submit from the "soft" account.

(replace operator, erwin, soft and reuti with your groups/users)


Another option could be to copy the jobscript in a directory which is writable 
by the users who are allowed to submit for another user. This user account runs 
a cronjob once a minute and picks up any script it finds therein and 
renames/removes it. It may be necessary to put all job options into the script 
itself though.

-- Reuti


>> Thought this isn't very elegant.
>> 
>> Regards,
>> Joseph David Borġ 
>> josephb.org
>> _______________________________________________
>> users mailing list
>> users@gridengine.org
>> https://gridengine.org/mailman/listinfo/users
> 
> _______________________________________________
> users mailing list
> users@gridengine.org
> https://gridengine.org/mailman/listinfo/users


_______________________________________________
users mailing list
users@gridengine.org
https://gridengine.org/mailman/listinfo/users

Reply via email to