Comments about your setup:
1) NIS is already lightweight itself. It will matter a little if you use LDAP. 2) I dont think your NFS is to blame. I have seen a setup worse than 40 students, using an older server and things work fine. Thoug if your NFS support cache, it can speed up file access. 3) I guess your java IDE or compiler is the one dragging you down. Most students servlets will be at most 1000 lines. That would translate to few kB. Few kBs are no sweat for NFS. Things that can slowdown NFS: streaming mp3, mpg, multiple netscape running on the NFS server, poor LAN connection, jammed LAN, etc. rowel On Tue, 26 Nov 2002, the CyberLizard wrote: > Anyway, here's a technical question: how does one go > about optimizing NIS and/or NFS so users can remotely > log-in to a Linux box (and keep a remote /home > directory)? We're setting up one of the IT Labs in my > school to dual-boot Linux/Win2K boxen, and we found > that NIS/NFS was too taxing on the network, especially > when a whole class of 40 students would be using their > home directories for compiling Java servlets... > <shudders> > _ Philippine Linux Users Group. Web site and archives at http://plug.linux.org.ph To leave: send "unsubscribe" in the body to [EMAIL PROTECTED] Fully Searchable Archives With Friendly Web Interface at http://marc.free.net.ph To subscribe to the Linux Newbies' List: send "subscribe" in the body to [EMAIL PROTECTED]
