Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!usc!sdd.hp.com!elroy.jpl.nasa.gov!lll-winken!unixhub!linac!att!pacbell.com!tandem!DSG.Tandem.COM!scott
From: scott@DSG.Tandem.COM (Scott Hazen Mueller)
Newsgroups: comp.sys.mips
Subject: MIPS NIS
Message-ID: <1991Jan25.225242.14654@tandem.com>
Date: 25 Jan 91 22:52:42 GMT
Sender: news@tandem.com
Reply-To: scott@dsg.tandem.com
Organization: Tandem Computers, Cupertino, CA
Lines: 45
Nntp-Posting-Host: work.dsg.tandem.com

I'm thrashing about, trying to get NIS to work properly on our MIPS Magnum
workstations.  These are pilot systems for my organization, and if I cannot
get them fully functional I will be recommending that we don't buy any more
of these until MIPS gets their act together.  However, maybe I'm just screwed
up and am not doing my setup correctly.

The basic issue here is that ypbind dies immediately when I start it from
/etc/init.d/netdaemons.  Our other Unix admin here says that she had that
problem under RISC/os 4.50, but thought it was fixed under 4.51, which is
what I'm working with.  By dying immediately, I mean that there is no
indication that ypbind even lasts a few seconds; a /etc/ypbind followed by
a /usr/bin/ypwhich in netdaemons yields the error 'ypwhich: bambi is not
running ypbind'.

The irritating part is that when I log into the workstation as soon as it
finishes booting in and type 'ypbind', it starts up fine.  Two successive
ypwhich commands yield 'Domain .dsg.tandem.com not bound.' and the name of
one of my Sun YP servers, respectively.

The material in the 'RISC/os System Administrator's Guide, Volume I' that
discusses NIS is spectacularly useless with respect to *exactly* how and when
you invoke ypbind in the startup process, so I'm not even confident I'm
starting ypbind correctly, though it strikes me as being particularly hard
to screw this up.

Since it may be relevant, my /etc/vis.conf contains:

passwd:         files nis
group:          files nis
host:           nis files
net:            nis files
netgroup:       nis files
services:       nis files
proto:          nis files

So, if anyone has made it through all of my long-winded description, is there
anyone out there who has seen and conquered this problem under 4.51, or who
has a fully functional yp running?  If so, I'd like to know what you did to
make it work.

Thanks,

-- 
Scott Hazen Mueller          scott@tandem.com          (apple|sun)!tandem!scott
Tandem Computers DSG, Unix System Administrator        +1 408 285 5762