Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!wasatch!cs.utah.edu!zeleznik From: zeleznik%cs.utah.edu@wasatch.utah.edu (Mike Zeleznik) Newsgroups: comp.sys.apollo Subject: Registry unavailable on DN 10000 Keywords: registry 10.1 rgyd accounts Message-ID: <2545@wasatch.utah.edu> Date: 16 Aug 89 20:47:38 GMT Sender: news@wasatch.utah.edu Organization: University of Utah CS Dept Lines: 23 We have a 10000 and a 3500 on an ethernet, running one master and one slave registry (10.1 on both machines). ** A number of times each day, when trying to login in to the 10K, the system complains that the network registry is unavailable, and must use the local one. If we try a few times, it will eventually suceed. This happens if the 10K is running the master or the slave. Has anyone seen this? Are the registries locked up when the master/slave are resyncing? I can't see why they couldn't be at least readable. ** Also, does anyone (HP/Apollo?) know if there are plans to replicate the master registry? In a big net, it seems a bit much to expect the single master to be available in order to make any updates (or am I missing something). Thanks in advance, Mike Michael Zeleznik Computer Science Dept. University of Utah zeleznik@cs.utah.edu Salt Lake City, UT 84112 (801) 581-5617