On Thu, 2002-10-10 at 18:32, Keith Winston wrote:
On Thu, 2002-10-10 at 17:38, Herman L. Knief wrote:
You might want to make sure it's actually running... look for the automount process, and make sure that you have valid automount maps (either local files, or nsswitch.conf setup to pull automount from NIS.)
In my limited NIS testing, I've found that mounting your /home/foo directory from NFS (automount or otherwise) can be painful if you are running a big fat desktop like KDE 3. KDE writes a ton of stuff there when it starts and that can make initial startup very, very slow unless you have a fast network and fast computers.
Now, I've only tested this with a small number of computers and not for an long time, so YMMV.
My mileage varies a lot from this actually. I never messed with automounter and we have about 12 boxes on NIS with set NFS mounts for the home dirs. I have heard other complaints from the developers about linux but the one about slow KDE response or response in general due to NFS writes is not one I have heard. How do other people usually go about setting this up? I just set the machine up as a NIS client and then set the home NFS mount up in the /etc/fstab. It works pretty quick IMHO. On the developers workstations I give them full ruin on /usr/local/share/<userid> so they have access to their own local disk but this is just a hack to keep all the user mp3s of the NFS server. :-> -- Johnathan Bailes BAE Systems ESI "UNIX was not designed to stop you from doing stupid things, because that would also stop you from doing clever things." - Doug Gwyn ---