SYSTEM@CRNLNS.BITNET (07/20/87)
Gentle VMS gurus, Two of our VAX/VMS systems here have a strange problem, namely that one must have SYSPRV in order for the SPAWN command to work. Without it, SPAWN fails immediately with the error message "%SYSTEM-F-NOPRIV, no privilege for attempted operation" without connecting the terminal to a subprocess. *flame on* It would be really nice if such messages said what privilege was needed and what operation was failing. *flame off* On the rest of our systems, the SPAWN command works as one would expect: only TMPMBX is needed. This is not intentional, but I can't find what is wrong. I don't remember doing anything out of the ordinary when I created the system disks. One is a 750 in a cluster with a private ra80 system disk, the other is a stand-alone 2 user microVax. Presumably something is protected against access, but I haven't been able to find it: All the .EXE files in SYS$SYSTEM and SYS$LIBRARY have world read and execute allowed. So do the directories. SET WATCH FILE/CLASS=ALL doesn't type anything whatsoever during the failure. I haven't been able to find any SYSGEN parameter that differs between the systems that should have this symptom. Various differences are identical to those on other systems that work. All of the accounts on the systems involved have sufficient quotas enabled. (The entries are identical to those on other systems that work.) I'm about to check the protection of all of the various system and user logical name tables, but was hoping somebody might have seen this before. Thanks, Selden E. Ball, Jr. (Wilson Lab's network and system manager) Cornell University NYNEX: +1-607-255-0688 Laboratory of Nuclear Studies BITNET: SYSTEM@CRNLNS Wilson Synchrotron Lab ARPA: SYSTEM%CRNLNS.BITNET@WISCVM.WISC.EDU Judd Falls & Dryden Road PHYSnet/HEPnet/SPAN: Ithaca, NY, USA 14853 LNS61::SYSTEM = 44283::SYSTEM (node 43.251)
SYSTEM@CRNLNS.BITNET (07/21/87)
My face is red. Long ago in a version of VMS far away, TMPMBX implied GRPNAM. With the coming of VMS 4.0 it did so no longer. A suggested way to make things work the way they used to was to use the logical name definition DEFINE/TABLE=LNM$PROCESS_DIRECTORY LNM$TEMPORARY_MAILBOX LNM$GROUP and to give the people who needed it GRPNAM. My affected systems had the definition but the accounts didn't have the privilege. sigh. One system (the microVax) needs group-wide mailboxes, so the accounts got the priv. The 750 didn't, so I eliminated the command from the system wide login command file. Sorry to have bothered you. Selden E. Ball, Jr. (Wilson Lab's network and system manager) Cornell University NYNEX: +1-607-255-0688 Laboratory of Nuclear Studies BITNET: SYSTEM@CRNLNS Wilson Synchrotron Lab ARPA: SYSTEM%CRNLNS.BITNET@WISCVM.WISC.EDU Judd Falls & Dryden Road PHYSnet/HEPnet/SPAN: Ithaca, NY, USA 14853 LNS61::SYSTEM = 44283::SYSTEM (node 43.251)