Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!cis.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!ucbvax!PAN.SSEC.HONEYWELL.COM!thompson
From: thompson@PAN.SSEC.HONEYWELL.COM (John Thompson)
Newsgroups: comp.sys.apollo
Subject: re: local registry
Message-ID: <9105231751.AA16344@pan.ssec.honeywell.com>
Date: 23 May 91 17:51:07 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 44



>     We have a disked DN3500 running SR10.2 using xdm for logging in.
>     It _used_ to have a rgyd but we've taken it off now (the problem
>     seemed to occur "not long" after doing this).
> 
>     When trying to log in, xdm seems to use the local registry for
>     passwords etc as most people can't log in, but some can. You can
>     rlogin and crp onto it fine from anywhere on the net, but you
>     (i.e. most people) just can't log in at the console! Fortunately,
>     the most frequent users tend to be able to log in (another
>     indication that it's using the local registry). Question is, WHY!?
>     Do I have to restart its rgyd? I've checked that /etc/passwd and
>     /etc/group have obty of passwd/group respectively; /sys/registry
>     looks OK (don't know what ACLs it should have). As I said, it
>     seems that only xdm has problems, so I'm lost. It's the only node
>     out of ~18 with this problem. help!

Check out the global brokers (glbd).  Use /etc/ncs/drm_admin to check on 
them and check the clock skews.  If they're too far out of whack, they 
don't tell each other what services are available.

Check out the registry with /etc/rgy_admin.  Use this to find out whether
your registry system still thinks there's a registry at the bad node.
If it does, use 'delrep' to get it gone.

Check out that node's information with /etc/ncs/lb_admin.  This is a dialog
based tool (w/ command line input, but that's yucky) that can do 'lookup' and
'clean' on the llbd database for a node, and on the glbd database that you 
specify OR THE DEFAULT THAT THE NODE FINDS.  Just click on the '<= local'
box in the dialog window to switch it to 'global =>', or enter 'use_broker global'
Then click on 'clean', or enter 'clean * * *' to have lb_admin check out all the
services.  If the glbd it selects isn't valid (or isn't talking w/ the rest of
them, you've found your problem.


-- jt --
John Thompson
Honeywell, SSEC
Plymouth, MN  55441
thompson@pan.ssec.honeywell.com

When in danger, when in doubt --
run in circles, scream and shout.