Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!emory!att!ucbvax!PAN.SSEC.HONEYWELL.COM!thompson From: thompson@PAN.SSEC.HONEYWELL.COM (John Thompson) Newsgroups: comp.sys.apollo Subject: re: mysterious hint file on HP/Domain/OS Message-ID: <9104051546.AA20778@pan.ssec.honeywell.com> Date: 5 Apr 91 15:46:19 GMT Sender: daemon@ucbvax.BERKELEY.EDU Organization: The Internet Lines: 42 <> > On Domain/OS SR10.2 some machines seem to have a problem with the file > /sys/node_data/hint_file. For example, if I log out ( under DM ) on the > machine itself, then go home to drink a cup of coffee and come back, > I MIGHT be able to login again because the DM does not yet display its > login pad. In short, logout is terribly SLOW. > Solution : remove the hint file and reboot the machine. If I remember correctly, the hint_file contains information concerning the network number(s) that the node is on (and that other nodes are?). Have these nodes been moved from one net to a new one recently? Have they been INVOLed recently? If so, you might have conflicting network IDs. You can discover this by running '/etc/rtsvc' on each node. Note the network ID that is listed. Unless you're running internet domain, they should all be the same. (It's possible to run 2 separate domain nets on the same line, but it's advised against.) Assuming this is the problem, decide on a separate network ID for each of the physical nets (ethernet, Apollo Token Ring, IBM Token Ring) that you have, and then go around to each node that is conflicting with the ID. Run "/etc/rtsvc -dev -net [-route | -noroute]" substituting the device (e.g. RING, ETH802.3_AT -- it'll be the same as what the rtsvc command displayed for you) and NETID for that device. If you're running internet domain, the gateway nodes will need to be told to offer routing service (w/ '-route'). If any non-gateways are currently offering it, turn it off (w/ '-noroute'). Otherwise, the -[no]route state is left at whatever it was. After you do all this, you may have some problems with your llbd, glbd, or rgyd processes. Hopefully, the nodes running glbd and rgyd will be correct. Otherwise, you will probably want to reboot them, and you may need to remove all but one glbd and rgyd, and then create the replicas again. -- jt -- John Thompson Honeywell, SSEC Plymouth, MN 55441 thompson@pan.ssec.honeywell.com Me? Represent Honeywell? You've GOT to be kidding!!!