[NTLUG:Discuss] Re: Distributing users via NIS -- NIS/yp client/slave notes

Minh Duong minh_duong at yahoo.com
Thu Aug 5 23:15:39 CDT 2004


> - Client Notes ...
> 
> 1.  Always make sure RPC/Portmapper (portmap) is
> running
> $ rpcinfo -p

I have 4 instances of ypserv, 1 yppasswdd and 4 ypbind

> 2.  In addition to the NIS/yp services (ypserv,
> yppasswd), make sure
> your NIS master and slave are also NIS clients
> (ypbind) too.

All three are running on both slave and master


> 3.  Linux GLibC 2.x has full support for name
> services switch
> (/etc/nsswitch.conf) configuration.  Solaris and
> select other unix
> flavors do as well.  Be sure that for _any_ NIS map
> you share has a
> "nis" entry on each client for the map (hosts,
> passwd, group, etc...).

nis is the first entry everywhere nis is listed
 
> [ SIDE NOTE:  On the master NIS/yp server, if you
> are sharing the same
> files as maps (e.g., /etc/hosts is shared out as
> NIS), consider putting
> a "+::::::" between the local/non-NIS (top) and
> NIS/yp (bottom) users so
> you don't have duplicate entries.  I.e., programs
> often stop parsing
> /etc/passwd as local when they reach the "+::::::"
> line, unless the
> NIS/yp client is down (this is an interesting study
> on its own). ]

 
> 5.  Just because you have NIS setup does _not_ mean
> the user's home
> directory is being shared out.  You do that
> _separately_, typically with
> NFS.  If you cannot login, make sure it's not
> because the user's home
> directory does not exist on the system where you are
> doing so.

I have copied the home directories.
 
> - NIS Slave Notes ...
> 
> 8.  Anytime you make a chance to a user account,
> consider cd /var/yp and
> doing a "make."  This _should_ update all makes, and
> push them to slave
> servers.

Thanks for everything but still not working. Any more
ideas?



		
__________________________________
Do you Yahoo!?
New and Improved Yahoo! Mail - Send 10MB messages!
http://promotions.yahoo.com/new_mail 



More information about the Discuss mailing list