> Again, we're an engineering shop and the users move lots of data > around, so NFS sucks over the WAN, though it's honestly tolerable for > home dirs. >
OOooohhh... I would caution against that idea. You might not know how much your home dir gets used. Every new shell runs another .bashrc, every little X movement reads another dot-file of various sorts ... etc. The main thing about the WAN is that it's very high latency, even for tiny little files, it'll take another 1 second delay ... over and over and over and over ... In the setup where I use the international NIS setup, the users have separate home directories in each country, but the path is always the same. So they're always /path/to/home but coming from a low-latency server. > What happens when someone changes their password on a remote site > without connection to the master? Duh... stupid question. It means > they can't change it. Sorry, low of sleep... Heheh. Right. > I guess my goal is to start moving to LDAP and possibly AD integration > down the line sometime, so I figure taking the baby steps with the > pam_ldap and pam_nss modules might be the way to go. But you're > making me think I should really just bite the bullet and finish the > NIS map merge and cleanup home dirs so that things aren't seperated > by NIS domain. No matter what, you're going to have to unify all the UID/GID/username mappings anyway. _______________________________________________ Tech mailing list [email protected] http://lopsa.org/cgi-bin/mailman/listinfo/tech This list provided by the League of Professional System Administrators http://lopsa.org/
