From owner-freebsd-isp  Tue Jun 25 23:55:55 1996
Return-Path: owner-isp
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id XAA12866
          for isp-outgoing; Tue, 25 Jun 1996 23:55:55 -0700 (PDT)
Received: from pelican.altadena.net (pelican.altadena.com [206.16.90.21])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id XAA12861
          for <isp@freebsd.org>; Tue, 25 Jun 1996 23:55:52 -0700 (PDT)
Received: by pelican.altadena.net (Smail3.1.29.1 #10)
	id m0uYoVx-0000RhC; Tue, 25 Jun 96 23:55 PDT
Message-Id: <m0uYoVx-0000RhC@pelican.altadena.net>
Date: Tue, 25 Jun 96 23:55 PDT
From: pete@pelican.altadena.net (Pete Carah)
To: isp@freebsd.org
Subject: Re: Setting up NIS/YP
In-Reply-To: <199606230427.AAA06450@ns2.harborcom.net>
Sender: owner-isp@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

In article <199606230427.AAA06450@ns2.harborcom.net> you write:

>> Can anybody out there help me get on track towards setting up an NIS
>> system with my existing FreeBSD machines ?
.....
>man yp
>is a great place to start. It is actually quite an informative 
>overview.

>man 5 passwd
>includes a good description of how the passwd file works with NIS.

>_Managing NFS and NIS_, by Hal Stern is also a good read (it's an 
>O'Reilly, got some funky porcupines or something on the cover).

>The section on NIS in the handbook is currently empty, but the above 
>should provide all the info you need.

Under -stable, various dates (this problem hasn't changed for a long time):

Now, all *I* need is to get our ypbind to handle an NIS+ server in 
compatibility mode; our SGIs under both 5.3 and 6.2 and the Sun 4.1.3 systems 
do fine but freebsd doesn't find the domain server (and we have a master 
and a slave, both in yp compat mode) (and fbsd ypbind won't connect even 
if you try to point out the server directly).

A kluge would be to run a yp slave server on one of the other Sun's but
I'd rather not do that :-)

-- Pete