I want to use an NFS mount of a server folder on my laptop. It mounts and
behaves as expected but it causes a real nuisance on a cold boot. The boot
process tries to mount the share but can’t because knetworkmanager doesn’t
set up the wireless connection until later. Result are a couple of long
waits until the boot proceeds to log the user on and gets a wireless
connection.
How do I get around that long (minutes) of waiting? Do I need to do the
mount after logging on or is there an appropriate setting for the NFS client
to basically fail with no wait until it has a network connection?
Haven’t tried this, but you could try a noauto in the fstab and then write an ifup/ifdown script to put in /etc/sysconfig/network/if-up.d that will mount the filesystem when the interface comes up. Note that scripts in that directory are actually symlinks to files in /etc/sysconfig/network/scripts, and the script should handle both up and down cases.
>
> Haven’t tried this, but you could try a noauto in the fstab and then
> write an ifup/ifdown script to put in /etc/sysconfig/network/if-up.d
> that will mount the filesystem when the interface comes up. Note that
> scripts in that directory are actually symlinks to files in
> /etc/sysconfig/network/scripts, and the script should handle both up and
> down cases.
That seems to work. I’ll have to see what happens when I connect to another
SSID - that may be the fly in the ointment. Looks like the script may have
to be a little more than my simple one but I should be able to muddle
through. Thanks.
>
> Will Honea;2247588 Wrote:
>> I want to use an NFS mount of a server folder on my laptop. It mounts
>> and
>> behaves as expected but it causes a real nuisance on a cold boot. The
>> boot
>> process tries to mount the share but can’t because knetworkmanager
>> doesn’t
>> set up the wireless connection until later. Result are a couple of
>> long
>> waits until the boot proceeds to log the user on and gets a wireless
>> connection.
>>
>> How do I get around that long (minutes) of waiting? Do I need to do
>> the
>> mount after logging on or is there an appropriate setting for the NFS
>> client
>> to basically fail with no wait until it has a network connection?
>>
>> –
>> Will Honea
>
> This worked for me
>
> In /etc/nfsmount.conf, change
>
> #Defaultvers=4
> to:
>
> Defaultvers=3
DUH! Did that on everything except this one laptop! Problem solved for
now. I’ll try and see how it works on a different access point where the
share is not available next but I should be OK.
> This worked for me
>
> In /etc/nfsmount.conf, change
>
> #Defaultvers=4
> to:
>
> Defaultvers=3
OK, back from some testing. The problem I was having with the long delays
for timeout were solved and I see now problem when connecting to other SSIDs
or hotspots where the NFS share is not available after setting the laptop as
above.
What I wanted was to run an email app as a shared app on the local network.
By mounting the NFS share over the local app, when I use a foreign network I
get the copy loaded onto the laptop. When I’m home, I get the networked
shared version so the networked version can interface to the email service I
use and do all the filtering , copying, and distribution necessary while I
can still access the account while on the road by going directly to the
email service and reading the mail w/o deleting it from the mail server.
Complicated reasons for this but it works.
Thanks again, even if it does make me feel stupid for having missed
something that obvious!