Path: utzoo!attcan!uunet!olivea!decwrl!sdd.hp.com!cs.utexas.edu!sun-barr!ccut!wnoc-tyo-news!etlcom!ulisvax!saka
From: saka@ulis.ac.jp (Tetsuo Sakaguchi)
Newsgroups: comp.sys.mips
Subject: Re: RISCos 4.51, NIS, and nameservice for NIS clients. Any ideas?
Message-ID: <6342@ulisvax.ulis.JUNET>
Date: 28 Jan 91 02:46:57 GMT
References: <5706@idunno.Princeton.EDU>
Sender: news@ulisvax.ulis.JUNET
Organization: Univ. of Lib. & Info. Sci., Tsukuba Japan
Lines: 31
Nntp-Posting-Host: ulisnrt

In article <5706@idunno.Princeton.EDU> svpillay@idunno.Princeton.EDU (Kanthan Pillay) writes:
>The problem: whenever any yp client binds to the MIPS box, then
>nameservice stops working on the clients. If the client binds to the
>Sun, everything works as advertised.

We found the same problem.  This is because the difference of
mechanizum of NIS between MIPS & Sun. (I thought)

>ypserv under IRIX includes a -i option which tells ypserv to look at

It seems to be IRIX uses NFS3.x.  Ypserv of NFS3.x lookup BIND when
started with option '-i'.
In SunOS4.x, ypserv lookup BIND when the map 'hosts' is made by
makedbm with option '-b'.
These NISs are use same policy that 'YPSERV lookups BIND'.

But, NIS of MIPS(RISCos4.5?) is different from above.
'CLIENTS lookup BIND specified by VIS'.
When any clients on MIPS want to get IP-addr, they look vis.conf and
lookup BIND if 'dns' is specified in vis.conf.
So, MIPS's ypserv does not lookup BIND.  (Clients NOT on MIPS don't
know vis.conf, and cannot get data from BIND.)

>                           I can simply turn off ypserv on the MIPS and
>continue running off the Sun for now.

We choose the same method.  I cannot find any other methods.

If I misunderstand, please tell me.
--
Tetsuo Sakaguchi. University of Library and Information Science, JAPAN.