dtrace discuss - Apr 2006 - dtrace privilege

I am trying to run some tests which need dtrace privilege. The tests is
being run as local user "gridadm".
I want to submit these tests script to Sun Grid Engine and run as
"gridadm"
user.

I added user "gridadm" to /etc/user_attr as following line:
gridadm::::defaultpriv=basic,dtrace_proc,dtrace_user,dtrace_kernel

When I run the "ppriv $$" from gridadm user shell, it give me the
right
privilege I need:

# ppriv $$
5501:   bash
flags = <none>
        E: basic,dtrace_kernel,dtrace_proc,dtrace_user
        I: basic,dtrace_kernel,dtrace_proc,dtrace_user
        P: basic,dtrace_kernel,dtrace_proc,dtrace_user
        L: all


But when I submit the following simple script to Grid Engine, it also run as
g"gridadm" user,
I don''t have the right privilege I need.  I am pretty sure the script
still
run under "gridadm" user,
but why it doesn''t have the right privilege??

====Script====#!/bin/ksh
echo "Running test as user $(logname)"
ppriv $$
============
===Output from script===Running test as user gridadm
29110:  -ksh /usr/sge/sge6/default/spool/nanonano/job_scripts/63122
flags = <none>
        E: basic
        I: basic
        P: basic
        L: all
====================
I tried to reboot the machines but still got the same result. What do I need
to do to gain dtrace privilege
when run under Grid Engine? Any idea?
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://mail.opensolaris.org/pipermail/dtrace-discuss/attachments/20060407/c3d24bf0/attachment.html>

>
>--Boundary_(ID_GZNrOtmXCpz9IbEr+Hb4Ww)
>Content-type: multipart/alternative;
> boundary="Boundary_(ID_NM7pD8sguf5nO2Ipp2mb6A)"
>
>
>--Boundary_(ID_NM7pD8sguf5nO2Ipp2mb6A)
>Content-type: text/plain; charset=ISO-8859-1
>Content-transfer-encoding: 7BIT
>Content-disposition: inline
>
>I am trying to run some tests which need dtrace privilege. The tests is
>being run as local user "gridadm".
>I want to submit these tests script to Sun Grid Engine and run as
"gridadm"
>user.
>
>I added user "gridadm" to /etc/user_attr as following line:
>gridadm::::defaultpriv=basic,dtrace_proc,dtrace_user,dtrace_kernel
>
>When I run the "ppriv $$" from gridadm user shell, it give me the
right
>privilege I need:
>
># ppriv $$
>5501:   bash
>flags = <none>
>        E: basic,dtrace_kernel,dtrace_proc,dtrace_user
>        I: basic,dtrace_kernel,dtrace_proc,dtrace_user
>        P: basic,dtrace_kernel,dtrace_proc,dtrace_user
>        L: all
>
>
>But when I submit the following simple script to Grid Engine, it also run as
>g"gridadm" user,
>I don''t have the right privilege I need.  I am pretty sure the
script still
>run under "gridadm" user,
>but why it doesn''t have the right privilege??
Because the grid engine doesn''t use PAM?


You need to fix the grid engine to setup the environment precisely
as pam does by calling pam_setcred.

Casper