Date: Sun, 7 Mar 1999 18:25:05 -0500 (EST) From: "Crist J. Clark" <cjc@cc942873-a.ewndsr1.nj.home.com> To: jktheowl@bga.com (John Kenagy) Cc: solca@fisicc-ufm.edu, cjclark@home.com, freebsd-questions@FreeBSD.ORG Subject: Re: NFS & NIS Problems Message-ID: <199903072325.SAA21111@cc942873-a.ewndsr1.nj.home.com> In-Reply-To: <199903060326.VAA01066@bga.com> from John Kenagy at "Mar 5, 99 09:26:02 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
John Kenagy wrote, > Otto E. Solares writes: > > "Crist J. Clark" wrote: > > > > > Otto E. Solares wrote, > > > > We have only a master server "zeus.adm.fisicc-ufm.edu", > > > > no slaves, one NIS domain "olympia.fisicc" and all clients > > > ^^^^^^^^^ > > > > are in time synch with zeus. > > > > > > > > The clients used to be in the same network with the > > > > server (192.168.1.0) but that was when we was setting up > > > > the clients 1 by 1 so we have no chance to see if has the > > > > same problems, now each lab contains like 40 clients, we have > > > > 4 labs (lab1: 192.168.2.0 lab2: 192.168.3.0 lab3:192.168.4.0 > > > > and lab4: 192.168.5.0) The clients are almost 95% the day > > > > in windows and a few days we have like 60 in FreeBSD > > > > (student projects), very tipically it hangs in X with the user > > > > logged in and display a message like RPC time out. > > > > > > I think this is your problem. NIS is intended to be run over a > > > LAN (it uses broadcast UDP messages). Client-server communications > > > start to get really funky on a WAN. The most straight forward way to > > > fix this is to run a slave server on each LAN. > > I will try the NIS slave, but what happens if i run a NIS slave in each > > client for speed, can be any trouble, suggestions??? > > I think you mean one slave in each lab, right? Then all of the > _other_ clients in the lab are served by it. So you will wind up with > one master and 4 slave servers, the rest are clients. I interpreted it to mean that every client was also slave server. Each client would be bound to itself. If you are not sure that one machine will always be up on each LAN running FreeBSD (which you hinted to as a possibility), this could be a work around. Just make sure that the startup of each client binds properly as do the slave servers. Otherwise, you could get a very complicated web of dependecies among the servers and clients, and with machines coming up and down, that could lead to annoying problems. As long as your NIS maps are not extroardinarily long and your network connections extraodinarily slow, I doubt there would be any noticable performance hits. -- Crist J. Clark cjclark@home.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199903072325.SAA21111>