Naming and Directory Services (DNS, NIS, and LDAP)

pc.yppasswdd Considers a Non-Restricted Shell ThatBegins With r to be Restricted1. Create /etc/default/yppasswdd that contains a special string:"check_restricted_shell_name=1".2. If the "check_restricted_shell_name=1" string is commented out, the ’r’check will no occur.Network or Servers Are OverloadedNIS can hang if the network or NIS servers are so overloaded that ypserv cannot geta response back to the client ypbind process within the time-out period.Under these circumstances, every client on the network experiences the same orsimilar problems. In most cases, the condition is temporary. The messages usually goaway when the NIS server reboots and restarts ypserv, or when the load on the NISservers or network itself decreases.Server MalfunctionMake sure the servers are up and running. If you are not physically near the servers,use the ping command.NIS Daemons Not RunningIf the servers are up and running, try to find a client machine behaving normally, andrun the ypwhich command. If ypwhich does not respond, kill it. Then log in as rooton the NIS server and check if the NIS process is running by entering the following.# ps -e | grep ypNote – Do not use the -f option with ps because this option attempts to translate userIDs to names, which causes more naming service lookups that might not succeed.If neither the NIS server (ypserv) nor the NIS client (ypbind) daemons are running,restart them by typing one of the following.# svcadm restart network/nis/serveror# /usr/lib/netsvc/yp/ypstop# /usr/lib/netsvc/yp/ypstartIf both the ypserv and ypbind processes are running on the NIS server, then runypwhich. Ifypwhich does not respond, ypserv has probably hung and should berestarted. While logged in as root on the server, restart the NIS service by typing oneof the following.118 System Administration Guide: Naming and Directory Services (DNS, NIS, and LDAP) • January 2005