On Sat, Mar 13, 2004 at 06:27:55PM -0800, Mr O wrote: > thing but I've seen posts on it. NFS likes to just drop it's > connection even though it shows as still mounted. Seems to be a > 2.6 thing. Anyone else experienced it yet?
I've had problems with the linux nfs-kernel daemon. It would die after a few mounts/umounts. It worked for one user, but wouldn't do for production. 2.4 kernel. Didn't find a solution. However now I'm using sunos with autofs. Question, does autofs use nfs? On my solaris box I've defined an nfs share with: $ cat /etc/dfs/dfstab share -F nfs -o rw=saraswati:parvati:lakshmi:vishnu -d "home dirs" /export/home Then I setup autofs on my linux laptop and on saraswati, the sunbox. It is clear that I could have 'share -F autofs...', however I don't and autofs works fine. In partial answer to my own question, typing mount on linux reveals: ... automount(pid2038) on /home type autofs (rw,fd=5,pgrp=2038,minproto=2,maxproto=3) saraswati:/export/home/cory on /home/cory type nfs (rw,addr=192.168.1.5) So I see it does use nfs. Can anyone clear up the relation? Why is it that although saraswati:/export/home is mounted, only /home/cory shows up instead of automounting the whole? Why would I specify 'share -F autofs' as opposed to what I have '-F nfs' ? And finally, I also have the option of cachefs. What is that good for? Cory -- Cory Petkovsek Adapting Information Adaptable IT Consulting Technology to Your (858) 705-1655 Business [EMAIL PROTECTED] www.AdaptableIT.com _______________________________________________ EuG-LUG mailing list [EMAIL PROTECTED] http://mailman.efn.org/cgi-bin/listinfo/eug-lug
