Rajko M. wrote:
On Thursday 16 August 2007 21:52, Art Fore wrote:
My question is, is this normal for NFS? Is there a timeout setting
somewhere you can make to prevent this hassle in the future or would I
just be better off not using NFS?
You can use NFS, but entries in /etc/fstab should be
On 2007/08/17 09:59 (GMT+0100) Dave Howorth apparently typed:
There's no need for noauto. Simply set the 'bg' option in /etc/fstab to
avoid having your system wait for non-essential mounts. Here's an
example of my nfs settings:
suse1:/home /home nfs rsize=8192,wsize=8192,intr,bg,noatime
Felix Miata wrote:
On 2007/08/17 09:59 (GMT+0100) Dave Howorth apparently typed:
There's no need for noauto. Simply set the 'bg' option in /etc/fstab to
avoid having your system wait for non-essential mounts. Here's an
example of my nfs settings:
suse1:/home /home nfs
On Fri, 2007-08-17 at 15:37 +0100, Dave Howorth wrote:
Felix Miata wrote:
On 2007/08/17 09:59 (GMT+0100) Dave Howorth apparently typed:
There's no need for noauto. Simply set the 'bg' option in /etc/fstab to
avoid having your system wait for non-essential mounts. Here's an
example of
I had some NFS shares from another computer and NFS client running for
those shares running on my suse 10.2 machine. The other machine is no
longer in existence, and booting into run level 5 was no problem,other
than I noticed it seemed to be slower. However, booting into run level
3, it would get
On Thursday 16 August 2007 21:52, Art Fore wrote:
...
My question is, is this normal for NFS? Is there a timeout setting
somewhere you can make to prevent this hassle in the future or would I
just be better off not using NFS?
You can use NFS, but entries in /etc/fstab should be set to noauto
