The FreeBSD NIS(YP) HOWTO : What do you need to set up NIS? : The ypbind daemon
Previous: The Software
Next: Setting up a NIS Client using Traditional NIS

6.3. The ypbind daemonNIS!ypbind daemon ypbind NIS daemon daemon!ypbind

The ypbind process can be forced to bind to a specific NIS server by specifing the server in /etc/rc.conf. For more info see the manual page for ypbind(8).

If the system cam resolv the hostnames without NIS, you may use the name, otherwise you have to use the IP address. ypbind 3.3 has a bug and will only use the last entry (ypserver ds9 in the example). All other entries are ignored. ypbind-mt handle this correct and uses that one, which answerd at first.

It might be a good idea to test ypbind before incorporating it in the startup files. To test ypbind do the following:

At this point you should be able to use NIS client programs like ypcat, etc... For example, "ypcat passwd.byname" will give you the entire NIS password database.

IMPORTANT: If you skipped the test procedure then make sure you have set the domain name, and created the directory

    /var/yp

This directory MUST exist for ypbind to start up succesfully.

If the test worked you may now want to change your startupd files so that ypbind will be started at boot time and your system will act as a NIS client. Make sure that the domainname will be set before you start ypbind.

Well, that's it. Reboot the machine and watch the boot messages to see if ypbind is actually started.


The FreeBSD NIS(YP) HOWTO : What do you need to set up NIS? : The ypbind daemon
Previous: The Software
Next: Setting up a NIS Client using Traditional NIS