Matt Stanley wrote: > I am running Red Hat 7.2 on multiple machines. For reference, they are > using the versions of ypbind, yp-tools and ypserv that come with 7.2. > My main use of NIS is to allow for SSO to multiple machines. However, > these machines do scientific computation and and I generally want them > to have a home directory on each machine they log into so logfile > traffic doesn't traverse the network.
I think you run the risk of confusing your users and making things more difficult for them, rather than better. Think for a moment about what other files live in the home dir, like ~/.bashrc, ~/.exrc, or ~/.pinerc... An approach I used when I was setting up a similar set of machines was to have a naming convention for local disk. The local storage was /scratch1, or /scratch1,2, and 3 on a few of my boxes. These were available as /net/<machine>/scratch1 for ease, although users were always encouraged to do their processing on the appropriate machine so I/O was local rather than NFS. Since I had groups of 2-6 machines in a department, a planned refinement that I never finished was another set of mappings like /depts/stat/<machine>/scratch<n>, as an indication of when traffic would be confined to the LAN. Otherwise it could be across the campus's 100Mb/sec backbone. ;-) > This also limits the amount of > NFS mounts each machine is required to have. Why do you care? If you use automount(autofs) only the required mounts will happen, dependencies between machines minimized. > According to the NIS white > paper, you can specify on the local machine using the passwd file a home > directory that overrides the NIS server default. An example would be: > > +username::::::/localsystem/username > > And this works great if you login via console, yet when you login via > telnet or ssh it reverts to the NIS server's home directory for the user > which is not NFS mounted on these machines. Is this a difference in how > PAM deals with console vs remote login? I don't know--that is a good theory. Check out /etc/nsswitch.conf for order of binding--I don't know if the "override" facility is supported. I used the facility you're talking about to disallow standard logins outside the user's home department, forcing them to use the NQS batch subsystem we had installed. The queuing system was quite valuable for about 10 of the 300 users with logins, since they had use of all the CPUs from the departments. > Any help is greatly appreciated! Good luck! Alan -- Alan Peery [EMAIL PROTECTED] _______________________________________________ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
