Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!mcnc!rti!sas!cole
From: cole@sas.UUCP (Tom Cole)
Newsgroups: comp.sys.dec
Subject: Re: Installing privileged images
Summary: also filename used on invocation can disable privileges
Message-ID: <1062@sas.UUCP>
Date: 8 Jun 89 01:03:22 GMT
References: <729@orbit.UUCP> <2993@rti.UUCP>
Organization: SAS Institute Inc.,Cary NC,25712
Lines: 28

In article <2993@rti.UUCP>, bcw@rti.UUCP (Bruce Wright) writes:
> In article <729@orbit.UUCP>, glamdrng@pnet51.cts.com (Rocky Lhotka) writes:
> > Does anyone know how to install an image requiring WORLD privs?  I have a
> > program which runs fine from my account (with WORLD) and is installed with
> > /PRIV=WORLD/OPEN/HEAD/SHARE but when run from a non-privileged account it does
> > not function...  Thanks in advance for any help!!
>  
> I assume you mean on VMS ... anyway.  If you have installed the image as
> shown above, then it should work (give you WORLD privilege when it's run).
> However, there are a few things you need to watch out for:
> 
> 						Bruce C. Wright

Just to add my own two cents worth, something that bit us on this was the
way you form the image name when you run the file.  If you specify an explicit
version number on the filename, even if it is the correct one that matches
the known file entry, then the system will not open the file using the known
file entry information, which means among other things that you won't get
the elevated priveleges when you run the program.  We found this because an
overly-helpful menu program tried to use fully qualified file names when
running images, and it disabled privileges, sharing, etc.

Hope this helps.

Tom Cole
SAS Institute

Declaimer:  Othello