Path: utzoo!attcan!uunet!ogicse!milton!etb
From: etb@milton.u.washington.edu (Eric Bushnell)
Newsgroups: comp.sys.apollo
Subject: Re: problems with root access
Summary: ncs, rgyd, glbd, llbd
Message-ID: <15545@milton.u.washington.edu>
Date: 31 Jan 91 18:51:14 GMT
References: <16199@sdcc6.ucsd.edu>
Organization: University of Washington, Seattle
Lines: 34

I've had similar problems. The replies I've seen
so far are good ones, but if your nodes are
*really* screwed, you may need more drastic measures.

As others have explained, the problem is that some or
all of the ncs daemons are not running/communicating.
The other problem is that you have to be root, or look
like root, to fix some of these. (catch-22)

Apparently, your node can't find or use the local registry,
/sys/registry/rgy_local. If you can, log in as user and
use rbak or /install/tools/rbak_sr10 to load in a local
registry from another node. (Make sure that one has a 
root account in it.)  Then you can get on as root and
clean up any corrupted files that may be causing your grief.
You may have to reboot and futz around a few times before
you get the right combination of fixes.

Here's another possibility: 
I have, on occasion, had to use /install/tools/rgy_create
to build a new registry from scratch, then reboot the node
and replace the registry with a backup copy.

I hope you don't have to resort to invol-ing the disk and 
reloading everything.

Now lemme tellya 'bout the time the power failed whilst changing
the network number, and when they woke up, none of 'em knew
where they were...

Eric Bushnell
UW Civil Engineering
etb@milton.u.washingto.edu
etb@augustus.ce.washington.edu