On May 11, 2010, at 6:49 PM, Todd Denniston wrote:
Brian Mathis wrote, On 05/11/2010 10:35 AM:
On Tue, May 11, 2010 at 10:01 AM, Rudi Ahlers rudiahlers@gmail.com wrote:
On Sat, May 8, 2010 at 5:12 PM, Brian Mathis brian.mathis@gmail.com wrote:
A simple solution would be to setup a cron job that runs every 5 minutes and does ls /mount/point > /dev/null
How would this fix the problem though? I'm asking cause I sit with the same problem, and haven't figured out yet to tell a remote server what todo if the NFS server is unavailable (be it network problems, maintenance, incorrect password, etc)
Rudi Ahlers
It doesn't fix it -- it's an ugly workaround -- but it works to keep them mounted. I don't know of an elegant solution if the NFS server goes away. I've seen it hang the clients until they timeout. Maybe an NFS expert on the list will be able to provide a better solution.
BTW, keeping the mount point busy pretty much invalidates the use of autofs
My critical servers are autofs and don't slam the nfs server.
However my clients do peg it so you are right.
If you really want permanent mounts, then I suggest going back to using fstab with the bg & intr options and ignore autofs, because it appears autofs only causes trouble for you.
Already do.
BTW what applications are you having autocompletion issues with? I have been using autofs for ~15 years and have only had issues with soft mounting causing data corruption.
Command line tab completion and a custom 3D script.
I think I'll do KISS on this one and just use fstab was I've been doing with bg, hard, intr.