Path: utzoo!attcan!uunet!lll-winken!cert!netnews.upenn.edu!kings.wharton.upenn.edu!lau From: lau@kings.wharton.upenn.edu (Yan K. Lau) Newsgroups: comp.sys.apollo Subject: Re: Registry problems AGAIN Message-ID: <31761@netnews.upenn.edu> Date: 25 Oct 90 19:03:58 GMT References: <9010250649.AA01789@vlsi-mentor.jpl.nasa.gov> Sender: news@netnews.upenn.edu Reply-To: lau@kings.wharton.upenn.edu (Yan K. Lau) Organization: A Private Heaven Lines: 33 In article <9010250649.AA01789@vlsi-mentor.jpl.nasa.gov> root@VLSI-MENTOR.JPL.NASA.GOV (The vlsi-mentor SysAdmin) writes: >What is this? I am logged in as 'root' and edrgy tells me I am >"not authorized to perform operation"? > >According to the properties, my SID *owns* the registry and the >files the registry is based on. What gives? > >---- >Dave Hayes dave@vlsi-mentor.jpl.nasa.gov > {ucbvax,ames}!elroy!vlsi-mentor!dave >"Attempt to find truth by realizing that it will generally find YOU." This is what I learned. It may not apply to your situation. Following the example instructions in creating registries, I set up them to be "owned" by %.sys_admin.%. This was done during the cvtrgy (converting 9.7 registries) and not the same as the acls of the directories. However, %.sys_admin.% is not the same as root.%.% which is different since root usually has access to everything. It turns out that if you are logged on as root on the machine with the master registries, you can perform add/changes, etc. anyway. This is either a feature or a bug. However, if you are logged onto another machine, then the %.sys_admin.% is enforced and you are not allowed to perform operations even if you are root. My solution: I created root.sys_admin.% so I can (if I have to) edrgy from any machine. I haven't actually tried edrgy as for example, lau.sys_admin so I don't know if that works. Hope this helps. Yan. )~ Yan K. Lau lau@kings.wharton.upenn.edu The Wharton School ~/~ -Sheenaphile- 128.91.11.233 University of Pennsylvania /\ God/Goddess/All that is -- the source of love, light and inspiration!