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 to importing net file system (NFS) and hang. This really proved to be a problem when I was trying to get compiz running, because going into runlevel 5 would lock up the desktop. Finally got out of it by going to installation DVD and selecting rescue 3, mounting the /home partion, and deleting the ~.kde/Autostart/compiz.sh script. Then I booted into run level 5 and went into YAST and removed the NFS client stuff. Now I can boot into run level 3 with no problem. 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? Art -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
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 for NFS shares that are not present all the time, like another desktop. The timeout exists, details you can see in man nfs but system should be able to start with or without NFS shares, unless they are part of basic file system, like /home. -- Regards, Rajko. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
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 set to noauto for NFS shares that are not present all the time, like another desktop.
The timeout exists, details you can see in man nfs but system should be able to start with or without NFS shares, unless they are part of basic file system, like /home.
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 0 0 You can man nfs for more information and this page also looks useful: http://www.linuxhomenetworking.com/wiki/index.php/Quick_HOWTO_:_Ch29_:_Remot... Cheers, Dave -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
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 0 0
I tried replacing noauto with bg, expecting to not need to manually mount, but it appears the mount never happens; at least, not within a few minutes of boot. How long until the mount should be completed?
You can man nfs for more information and this page also looks useful: http://www.linuxhomenetworking.com/wiki/index.php/Quick_HOWTO_:_Ch29_:_Remot... -- " It is impossible to rightly govern the world without God and the Bible." George Washington
Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://mrmazda.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
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 rsize=8192,wsize=8192,intr,bg,noatime 0 0
I tried replacing noauto with bg, expecting to not need to manually mount, but it appears the mount never happens; at least, not within a few minutes of boot. How long until the mount should be completed?
The mount should happen during boot of the client if the NFS server is up. If the NFS server is down, the client should boot without the mount and the mount should appear when the server becomes available. I had a problem yesterday with an old system that wasn't mounting NFS disks at boot. I went into YaST and made it rerun its NFS client setup. That fixed it. I suspect YaST had first been run with no automatic NFS mounts so wasn't starting the NFS client at boot-time, then we'd edited fstab by hand, so rerunning YaST made it notice that it needed to start the NFS client. I can't guarantee that my guess is correct, or that YaST works the same way on recent systems, or that this is your problem :) But it might be worth a try! Cheers, Dave -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
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 my nfs settings:
suse1:/home /home nfs rsize=8192,wsize=8192,intr,bg,noatime 0 0
I tried replacing noauto with bg, expecting to not need to manually mount, but it appears the mount never happens; at least, not within a few minutes of boot. How long until the mount should be completed?
The mount should happen during boot of the client if the NFS server is up. If the NFS server is down, the client should boot without the mount and the mount should appear when the server becomes available.
I had a problem yesterday with an old system that wasn't mounting NFS disks at boot. I went into YaST and made it rerun its NFS client setup. That fixed it.
I suspect YaST had first been run with no automatic NFS mounts so wasn't starting the NFS client at boot-time, then we'd edited fstab by hand, so rerunning YaST made it notice that it needed to start the NFS client.
I can't guarantee that my guess is correct, or that YaST works the same way on recent systems, or that this is your problem :) But it might be worth a try!
Cheers, Dave I would suggest to use autofs. The mounts are base on the user.It will only mount when a user logs in. -- Joseph Loo jloo@acm.org
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (5)
-
Art Fore -
Dave Howorth -
Felix Miata -
Joseph Loo -
Rajko M.