Just wanted to say I got this working, and it wasn't anything out of the
ordinary. The directory which contained the scripts had two very similarly
named ones. Well, I added the wrong one of the two to the rights profile, and
never even noticed it until this morning. I probably looked right at i
Please send the following files:
/etc/security/exec_attr
/etc/security/prof_attr
/etc/user_attr
Also send the output of profiles -l for the user and the role.
BTW you shouldn't need euid=0 and proc_owner you should only need
proc_owner.
--
Darren J Moffat
You guys are great. Darren, Scott, thank you!
This message posted from opensolaris.org
As Per Darren, with my response:
>>What login shell are you using ?
Tried with ksh and pfksh.
>>In some shells kill is a shell builtin: (pf)sh, (pf)ksh, zsh, tcsh.
>>Does it work if you type the full path, ie /usr/bin/kill ?
Sure enough, when proc_owner is assigned to the role, just typing "kil
I tried doing something more basic, and to me, it seems as though adding
commands into a rights profile isnt working at all.
I created a rights profile titled Basic Test User, which was identical to Basic
Solaris User, so I could modify it and not disrupt the original. I then added
the command
I wish I could say that helped, but it was already using /bin/ksh, and I also
tried /bin/pfksh
I added the rights profile to a role, and added the user to the role. I then
tried the same thing but through the role rather than user, and got the same
result, except the log showed the role name as
James Hardwick wrote:
> So I have been working in Solaris, and *nix in general recently for the
> first time in a long long while. Trying to do various things which may
> be easy to you guys, but not so much to me. Anyways, here goes it...
>
> I am currently running in Solaris 10 w/ TX, build 42
