Configuring the Network Information Service (NIS)

Modifying server attributes

The following sections explain how to modify NIS server attributes. In general, when modifying an attribute on an NIS server, the other servers should be updated with the change by executing a ypmake command. Refer to the appropriate section for more details.

See also:

Propagating maps

When a new NIS map is created on the master server in an NIS domain, the new map must be propagated, or ``pushed'', to all NIS servers in that domain. NIS maps can be pushed to the servers with either the yppush(NADM) or the ypmake(NADM) command.

To create an NIS map on the master server and to push this map to all the servers in an NIS domain, follow these steps:

Log in as root on the master server.
Change to the /etc/yp directory.
Enter:
```
   ypmake mapname
```

To only push a map's changes to the other NIS servers, without creating a new NIS map, use the yppush command as follows:

Log in as root on the master server.
Change to the /etc/yp directory.
```
   yppush mapname
```

See also:

``NIS maps''

Modifying the remote binding mode

The command

   ypbind -ypset

executed on the local machine says that a ypset(NADM) command issued from any machine may change the binding on the local machine. This option poses serious security risks and should only be used for debugging the network from a remote machine.

See also:

``NIS binding''

Modifying the local binding mode

The command

   ypbind -ypsetme

executed on the local machine says that a ypset(NADM) command may be used to set the binding of the local machine only if the ypset command is issued from the local machine.

See also:

``NIS binding''