Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!seismo!husc6!mit-eddie!ll-xn!ames!sdcsvax!ucbvax!CU20B.COLUMBIA.EDU!OC.PREMA From: OC.PREMA@CU20B.COLUMBIA.EDU (Prema Nair) Newsgroups: comp.os.vms Subject: process privileges Message-ID: <12321781240.160.OC.PREMA@CU20B.COLUMBIA.EDU> Date: Mon, 27-Jul-87 16:45:54 EDT Article-I.D.: CU20B.12321781240.160.OC.PREMA Posted: Mon Jul 27 16:45:54 1987 Date-Received: Thu, 30-Jul-87 02:09:46 EDT Sender: daemon@ucbvax.BERKELEY.EDU Distribution: world Organization: The ARPA Internet Lines: 13 I have noticed that some users who have been given extra priveleges like PHY_IO, LOG_IO, and SHARE cannot set their privs in a spawned process, unless they are DEFAULT PRIVS as well. << the bottomline here is that if you SET/PROC/PRIV= in your main process and then create the subprocess, then both your main and subprocess will have same privileges without assigning PHY_IO, LOG_IO and SHARE as default privs in UAF. But if you want to simply set privs in a spawned process without assigning default privs or not setting privs in main process -- -------