home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.sys.next.misc:19625 comp.sys.next.sysadmin:5199
- Path: sparky!uunet!gatech!psuvax1!rutgers!igor.rutgers.edu!aramis.rutgers.edu!ssietz
- From: ssietz@aramis.rutgers.edu (Steven Sietz)
- Newsgroups: comp.sys.next.misc,comp.sys.next.sysadmin
- Subject: NeXT Netinfo Troubles
- Keywords: Help!
- Message-ID: <Sep.15.08.50.15.1992.27292@aramis.rutgers.edu>
- Date: 15 Sep 92 12:50:15 GMT
- Followup-To: comp.sys.next.sysadmin
- Organization: Rutgers Univ., New Brunswick, N.J.
- Lines: 27
-
-
- I was messing around with my cube yesterday and I think I confused netinfo.
-
- Here's the deal:
-
- My cube died last month and had it shipped out. In the meantime, I changed
- the netinfo on its clients - nextstations (from netinfo network to non-netinfo)
- I get the cube back and boot it up. The previous netinfo db was restored
- and all looked well. I changed the configs on the nextstations back to
- netinfo and rebooted. They couldn't find their netinfo server.
-
- I was able to connect to the station's netinfo db from the cube so I knew I
- was close. However, I believe I started copying the broadcasthost entry
- between domains. This caused my cube's netinfo to shut down. I am logged in
- as myself but cannot su to root, run netinfo, or even an ls -l. (Plain ls
- works). Nor can I do an nidump of the / domain.
-
- What should I do? I presume I must reboot into single user mode but don't know
- my way around niutil or niload. Help!!
-
- -Steve-
-
- PS. These NeXT machines sure aren't very forgiving!!
- --
- Steven Sietz | Internet: ssietz@cs.rutgers.edu
- 77A West Bluebell Lane | uucp: {backbone}!rutgers!cs.rutgers.edu!ssietz
- Mount Laurel, NJ 08054 |
-