Linux nis not updating map make
You can verify this by running 'ypwhich' you will see that you are not currently bound to a NIS domain.
Try following the procedure in Section 3.2 precisely.
If you see it, you should find out what your servers are bound to: # ypwhich If you find your master (or slave) is bound to something other than the master, force it to bind to the master by killing ypbind on that machine and then restarting it like this: # ypbind -ypsetme # ypset master-nis-ip Q: Why do I get the following error when I run a make: "can't get address for server ." A: There is a blank line in your ypservers map.
You can verify this by running the following: ypcat -k ypservers Remove the blank line by following the standard procedure for adjusting the ypservers map that is described in Section 3.3.
You do not have to be the superuser to use these commands.
The most commonly used NIS commands are: ypcat, ypmatch, ypwhich.
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.
Makefile If the files are substantially different, you should revert to the original, and see if that fixes the problem.
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.
"Running /var/yp/Makefile..." "make: Fatal error: No arguments to build" "Error running Makefile." ... Copy it over before rerunning ypinit: # cp /usr/lib/NIS.
Makefile /var/yp/Makefile # cd /var/yp # ypinit -m Q: Why does 'ypinit -s' crash with the following error, when trying to initialize a slave: "can't bind for domain " A: Your slave was not running ypbind, or it does not have access to NIS currently.
As with most config files you should consider making a backup copy of the file before making changes.