Path: utzoo!utgpu!watserv1!watmath!att!dptg!ulysses!andante!mit-eddie!bu.edu!rpi!zaphod.mps.ohio-state.edu!usc!ucsd!helios.ee.lbl.gov!pasteur!ucbvax!VLSI-MENTOR.JPL.NASA.GOV!root
From: root@VLSI-MENTOR.JPL.NASA.GOV (The vlsi-mentor Super User)
Newsgroups: comp.sys.apollo
Subject: Re:  RGYD at 10.2
Message-ID: <9007202107.AA23580@vlsi-mentor.jpl.nasa.gov>
Date: 20 Jul 90 21:07:27 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 22
X-Local-Date: 20 Jul 90 14:07:27 PDT

>When /etc/rgyd goes berserk, it is frequently caused by a failure in the underlying
>NCS support (/etc/ncs/llbd and/or /etc/ncs/glbd), which in turn relies on the TCP/IP
>services to be up and running. Yes, I know that NCS is *supposed* to be able to use

Yup. I was running a 10.1 glbd and a 10.2 llbd. Silly me! 

Thanks to all who responded (George Zipperlin and David Krowitz) for the help. 
It works now. I still have a question:

>If TCP/IP services are working correctly, then another possible cause is a global
>location broker database problem. If you run more than a single copy of /etc/ncs/glbd
>on your network (and it is *highly* recommended that you do so) and the system clocks
>on the nodes running each of the copies are not within 5 minutes of each other, then
>changes to the glbd database made on one machine may not get propagated to the other
>machines. You can use /etc/ncs/drm_admin to check this and to forcably merge the db
>contents.

Why is it reccommended to run more than one copy of glbd? When is HPOLLO going
to figure out a way to sync their clocks?
----
Dave Hayes  dave@vlsi-mentor.jpl.nasa.gov   dave%vlsi-mentor@jpl-mil.jpl.nasa.gov
"The word 'choice' is a fraud when one is taught what to choose."