NIS Account creation

[rajesh73]

After that user account creation , we try to put make , but it exits imediately

#make
gmake[1]: Entering directory `/var/yp/NIS'
Updating netid.byname...
gmake[1]: Leaving directory `/var/yp/NIS'
#

normally once type make, this command update passwd.byname, passwd.uid, groupby.name,group.bygid after that netid.byname . but yesterday i try to pur make, this not update properly, please find the above error. what service we need to restart without affect any servies.

[Matti_Kurkela]

That is not an error: the make command seems to think that only the source file for the "netid.byname" map has been changed since the NIS maps were created, so only that map needs to be updated.

Perhaps someone or something already ran the "make" command for you? Use "ypcat passwd | grep <username>" to see if the <username> is already listed in the NIS maps. Or check the timestamps of the passwd.byname and passwd.byuid files in the /var/yp/NIS directory, and compare them to the timestamp of /etc/passwd.

Normally, the /etc/passwd and /etc/group files on the NIS master are used as the source files for the creation of NIS user and group maps. But it is possible to change this, e.g. to allow the NIS master server to have a different set of users than the rest of the NIS domain. In that case, the YPSRCDIR, YPPWDIR, GROUP and/or PASSWD variables in the Makefile have probably been modified to use some non-default passwd and group files.

There are many other custom configurations that can be achieved by changing the variables in the beginning of the /var/yp/Makefile. Without seeing the values of these variables, it is impossible to know for sure what is actually causing your issue.

[rajesh73]

pls find the output

ypcat passwd | grep rajesh
No such map passwd.byname. Reason: Can't bind to server which serves this domain

[rajesh73]

hi ,

pls confirm any file is corrept or we need to restart service

[Matti_Kurkela]

> No such map passwd.byname. Reason: Can't bind to server which serves this domain

Maybe the NIS server has no ypbind process running? (The NIS server can serve the NIS database to other hosts without it, but having ypbind running would allow NIS troubleshooting on the server.)

Try running the ypcat command on another host that definitely is a NFS client. If the same error is returned, then there is a problem with the ypserv process on the NIS server host; if not, the problem is with the ypbind process on the host that produces the error.

Is the NIS domainname set correctly? Based on the pathname /var/yp/NIS, the NIS domainname should apparently be "NIS". Run "ypdomainname" or "nisdomainname" to display the current NIS domain name.