If the above commands do not make it clear what your problem is, you might want to consult the NIS files.
If a NIS server is doing something incorrect during map distribution, you should look at the /var/yp/Makefile on the NIS server.
You can verify this by running 'ypwhich' you will see that you are not currently bound to a NIS domain.
Q: Why is my change to the NIS maps not showing up? You can verify this by examining the map with ypcat.
To resolve the problem, go to the NIS master and make the files: # cd /var/yp # make A2: If make has been run, you are probably bound to a NIS slave which is not getting updates.
Q: Why do I get the following errors when making the netgroup map: "entry too big, problem storing netgroup" "error code 1" A: netgroup maps have a maximum of 200 entries, or 1024 characters per line.
You will get the above errors if you have a netgroup larger than this.
It is always best to just run 'make' and let the processes make and distribute whatever maps have changed.
Running make source-file may not update all maps that require changes.
As with most config files you should consider making a backup copy of the file before making changes.
If a Solaris NIS Client is not correctly accessing NIS, you should consult the file /etc/nsswitch.conf, and verify that it includes a reference to NIS.
-or- Q: Why do I get the following message when doing a make: "Can't bind master to send ypclear message to ypserv for map mail.aliases." There are two solutions to this problem.
If you are running a mix of operating systems on your network (Solaris, IRIX, HPUX) you should probably consider the second solution since the maps should be built by the slave servers themselves as the dbm format may be different on different OS'es.
It is particularly helpful to compare the Makefile to the original one that was shipped with the system: %% diff /var/yp/Makefile /usr/lib/NIS.