17.6. Setting Up an NIS Slave Server

Slave NIS servers are used in a similar way to secondary DNS servers—they keep a copy of the tables held by the master server, and they can be used by clients if the master fails or is slow to respond. If you are using NIS on a very large network that has multiple LANs connected by slow links, it may also make sense to put a slave server on each LAN so that clients can use it instead of the master.

On OpenLinux, there is no way to setup a slave server using Webmin, due to the unique NIS configuration files used by the distribution. On all other versions of Linux, the steps to set up a system as a slave server are:

1.
On the module's main page, click on the NIS Server icon. This will take you to the server configuration form, shown in Figure 17.2.

2.
Set the Enable NIS server? field to Yes.

3.
Enter the master server's domain into the NIS domain field.

4.
Change the Server type to Slave of server, and enter the IP address of the master into the field next to it. None of the other fields need to be touched, because they all relate to running a master server.

5.
Click the Save and Apply button. The server should be started immediately, and configured to start at boot time.

Make sure that the master server has the address of this slave entered into the Slave servers field on the server configuration form. It should also have the Push updates to slave servers? option enabled, so that any changes to tables will be immediately sent to the slaves. If not, you can use the yppush command to send the contents of an NIS table to some or all slave servers.

..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset
3.139.82.234