Re: NIS setup

[Oliver Fromme <check+irjjo300rsut1zoy@xxxxxxxxxx>]

Chuck Tuffli <ctuffli@xxxxxxxxx> wrote:
 > I'm trying to setup a NIS client for the first time and am having some
 > trouble. I used an older FreeBSD article as a guide
 > (http://www.freebsddiary.org/nis-client.php), and wanted to know if
 > there are any Dragonfly specifics that I needed to be aware of. The
 > machine is running 1.3.7-DEVELOPMENT built from sources a couple of
 > days ago. Generically, NIS doesn't seem to work. Specifically,
 > something like the below errors out.
 > 
 > sldev12-l# ypcat passwd
 > ypcat: no such map passwd.byname. reason: Can't bind to server which
 > serves this domain

What does the "ypwhich" command print?

 > sldev12-l# rpcinfo -p
 >   program vers proto   port
 >    100000    2   tcp    111  portmapper

Is that all?  Here it says:

# rpcinfo -p
program vers proto   port
       100000    2   tcp    111  portmapper
       100000    2   udp    111  portmapper
       100004    1   udp   1015  ypserv
       100004    2   udp   1015  ypserv
       100004    1   tcp   1023  ypserv
       100004    2   tcp   1023  ypserv
       100007    2   udp   1001  ypbind
       100007    2   tcp   1021  ypbind

Note that all of my NIS clients are also NIS slave servers
and bind to themselves.  That's why ypserv appears above,
too.  The advantage is that the clients are mostly immune
against server problems (downtime), because each client
keeps a local copy of the maps.  It also keeps network
traffic down.  Only when something changes on the master,
the changes are pushed to all slaves (i.e. to all clients).

Best regards
   Oliver

-- 
Oliver Fromme,  secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing
Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd

Any opinions expressed in this message may be personal to the author
and may not necessarily reflect the opinions of secnetix in any way.