Hi all, I've noticed that none of my nfs directories mount at bootup despite being set as auto in the /etc/fstab file. Issuing the "mount -a" command as root mounts them immediately without any problems. Does anyone know why they fail to mount initially? Would be grateful for any advice, tips or ideas. TIA Eddie
Eddie said:
Hi all,
I've noticed that none of my nfs directories mount at bootup despite being set as auto in the /etc/fstab file. Issuing the "mount -a" command as root mounts them immediately without any problems.
Does anyone know why they fail to mount initially? Would be grateful for any advice, tips or ideas.
Eddie, Are you using a wireless connection? I have had a similar problem with my wireless connected laptop. My problem was caused by the NFS shares being mounted before the wireless card had actually come up. All you need to do is change when nfs shares are mounted, by changing the start number for the script in /etc/init.d/rc5.d and rc3.d I have set mine so it loads just before X starts that gives the wireless card time to initialise. Be warned though every time you run SuSEconfig such as after adding new software, SuSE config resets the start order and you will need to make the change again. Probably SuSEconfig can be told not to reset the runlevels, bu t I haven't bothered to look. David -- David Bottrill david@bottrill.org
David Bottrill wrote:
Are you using a wireless connection? I have had a similar problem with my wireless connected laptop. My problem was caused by the NFS shares being mounted before the wireless card had actually come up. All you need to do is change when nfs shares are mounted, by changing the start number for the script in /etc/init.d/rc5.d and rc3.d I have set mine so it loads just before X starts that gives the wireless card time to initialise.
Be warned though every time you run SuSEconfig such as after adding new software, SuSE config resets the start order and you will need to make the change again. Probably SuSEconfig can be told not to reset the runlevels, bu t I haven't bothered to look.
I have this problem too - there's an option in /etc/sysconfig in Yast2 to pause the boot process for a while after bringing up the network if your network connection takes a while to come up, but it doesn't work for wireless. Like you, I moved NFS further down the boot order, but found YaST2 kept resetting it - I did look in YaST2 and at the /etc/sysconfig scripts to try and figure out how to fix this, but couldn't figure out where SuSE store this data. -- Geoff Beaumont geoffbeaumont@stormhammer.com
On Thu, 2003-07-03 at 16:17, Geoff Beaumont wrote:
Like you, I moved NFS further down the boot order, but found YaST2 kept resetting it - I did look in YaST2 and at the /etc/sysconfig scripts to try and figure out how to fix this, but couldn't figure out where SuSE store this data.
Try putting "xdm" or "splash_late" or one of the other late starting scripts on the Required-start line in /etc/init.d/nfs, then "insserv -r nfs" and "insserv nfs". That should put the nfs script very late in the boot order.
On Thursday 03 July 2003 3:40 pm, Anders Johansson wrote:
On Thu, 2003-07-03 at 16:17, Geoff Beaumont wrote:
Like you, I moved NFS further down the boot order, but found YaST2 kept resetting it - I did look in YaST2 and at the /etc/sysconfig scripts to try and figure out how to fix this, but couldn't figure out where SuSE store this data.
Try putting "xdm" or "splash_late" or one of the other late starting scripts on the Required-start line in /etc/init.d/nfs, then "insserv -r nfs" and "insserv nfs". That should put the nfs script very late in the boot order.
Cheers - wasn't quite that simple, as quite a few boot scripts depend on $remote_fs. I gave nfs a dependancy on postfix and removed the dependancy on $remote_fs from one or two other scripts (nothing that will cause a problem in this case). Glad I'm not the guy at SuSE who has to figure out a dependancy structure that'll work for everyone... Cheers, -- Geoff Beaumont geoffbeaumont@stormhammer.com
On Thursday 03 Jul 2003 10:42 pm, Geoff Beaumont wrote:
On Thursday 03 July 2003 3:40 pm, Anders Johansson wrote:
On Thu, 2003-07-03 at 16:17, Geoff Beaumont wrote:
Like you, I moved NFS further down the boot order, but found YaST2 kept resetting it - I did look in YaST2 and at the /etc/sysconfig scripts to try and figure out how to fix this, but couldn't figure out where SuSE store this data.
Try putting "xdm" or "splash_late" or one of the other late starting scripts on the Required-start line in /etc/init.d/nfs, then "insserv -r nfs" and "insserv nfs". That should put the nfs script very late in the boot order.
Cheers - wasn't quite that simple, as quite a few boot scripts depend on $remote_fs. I gave nfs a dependancy on postfix and removed the dependancy on $remote_fs from one or two other scripts (nothing that will cause a problem in this case).
Glad I'm not the guy at SuSE who has to figure out a dependancy structure that'll work for everyone...
Cheers, -- Geoff Beaumont geoffbeaumont@stormhammer.com
Thanks to all. I resolved it by editing the /etc/init.d/nfs file. I changed "mount -at nfs rc_status sleep 1" to "mount -at nfs & rc_status sleep 2" -- Eddie
Op donderdag 3 juli 2003 16:17, schreef Geoff Beaumont:
David Bottrill wrote:
Are you using a wireless connection? I have had a similar problem with my wireless connected laptop. My problem was caused by the NFS shares being mounted before the wireless card had actually come up. All you need to do is change when nfs shares are mounted, by changing the start number for the script in /etc/init.d/rc5.d and rc3.d I have set mine so it loads just before X starts that gives the wireless card time to initialise.
Be warned though every time you run SuSEconfig such as after adding new software, SuSE config resets the start order and you will need to make the change again. Probably SuSEconfig can be told not to reset the runlevels, bu t I haven't bothered to look.
I have this problem too - there's an option in /etc/sysconfig in Yast2 to pause the boot process for a while after bringing up the network if your network connection takes a while to come up, but it doesn't work for wireless.
Like you, I moved NFS further down the boot order, but found YaST2 kept resetting it - I did look in YaST2 and at the /etc/sysconfig scripts to try and figure out how to fix this, but couldn't figure out where SuSE store this data.
-- Geoff Beaumont geoffbeaumont@stormhammer.com
I have this problem too. But it only happened when I moved from a 100M to slower 10M network. May that give a clue? There is a variable called WAIT_FOR_INTERFACES in /etc/sysconfig/network/config that seems to slow down the process. # # Some interfaces need some time to come up/to have a connection # WAIT_FOR_INTERFACES is a global wait for all Interfaces in # Seconds. If empty no Wait occurs. # WAIT_FOR_INTERFACES= It will just sleep the seconds defined by the variable: [ ! -z "$WAIT_FOR_INTERFACES" ] && sleep $WAIT_FOR_INTERFACES May this work? -- Richard Bos Without a home the journey is endless
participants (6)
-
Anders Johansson -
David Bottrill -
Eddie -
eddie
-
Geoff Beaumont -
Richard Bos