> 
> 2. Use getrealpath() to determine the canonical
> pathname for the file.
> 
> 3. Look up the canonical pathname in the user's
> profiles to find the 
> attributes (user/group ids and privileges).
> 

Scott:

My execution profiles database has an executable that has a symlink in the 
pathname (for historical reasons and now our users are used to it).  Now pfexec 
is failing with permission denied because of the above logic.

What are my options?
a) Educate my users to use the new pathname
b) Remove the symlink

Thanks in advance,
-- prasad
--
This message posted from opensolaris.org

Reply via email to