Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!sdd.hp.com!caen!uwm.edu!bionet!agate!hailstorm.Berkeley.EDU!dpassage From: dpassage@hailstorm.Berkeley.EDU (David G. Paschich) Newsgroups: comp.sys.apollo Subject: Re: Unable to update /etc/passwd or registry. Not owner Summary: Apollo gets it wrong againg Keywords: registry not owner error inconsistent Message-ID: <1991Mar18.230943.11632@agate.berkeley.edu> Date: 18 Mar 91 23:09:43 GMT References: <50709a54.20b6d@apollo.HP.COM> Sender: usenet@agate.berkeley.edu (USENET Administrator) Organization: UC Berkeley Open Computing Facility Lines: 22 In article <50709a54.20b6d@apollo.HP.COM> pato@apollo.HP.COM (Joe Pato) writes: >The "Not owner" error is generated upon an authentication failure when >trying to update data in the network registry. In general this will >happen if the user is not authorized to update the data (for password >and shell changes, this means the user is updating another user's account >and the active user is not the administrator for that account). The >error can also occur if the user has not established the proper authentication >key on the local machine. This will happen if the user logged in off of >the local registry or used "crp -me" or rlogin without a password. In each >of these cases the chsh process does not have access to the proper >authentication key - and this will prevent the authentication protocol from >running correctly which in turn causes the registry server to deny >update access. This error continues to occur under those conditions, i.e., the person logged in directly on console or used the crp or rlogin programs with a password. Again, our system is running SR 10.3 on 35 and 4500's with 17 nodes and four registry sites. glbd is running on the node with the master registry. David G. Paschich Open Computing Facility Site Manager UC Berkeley dpassage@ocf.berkeley.edu "I'm so happy I can't stand myself" -- Adam Glass