On Sat, Mar 7, 2009 at 3:18 PM, ./aal wrote:
>
> On Fri, Mar 6, 2009 at 12:17 AM, Brett Miller wrote:
>>
>>
>> On Mar 5, 2009, at 4:25 PM, Don Delp wrote:
>>
>>>
>>> At home, my main desktop has the biggest hd in the house and I've
>>> shared it out through NFS. It's handy and easy to work with, until I
>>> leave the house. I don't mind losing access to the files enough to
>>> set up a VPN, but my local NFS client has a tantrum when anything even
>>> thinks about the mounted files. For instance, the df command will
>>> hang and I can't view the "Storage Media" page in Dolphin to manage
>>> other attached devices.
>>>
>>> As long as I remember to umount the remote share before I leave the
>>> house, there are no problems. Unfortunately, I don't often remember.
>>> What I do remember is to put the laptop to sleep before leaving. I
>>> think the best way to fix this would be to have the computer umount
>>> any remote shares as part of the suspend or hibernate process. Then,
>>> if I can have fries with that, I'd love to have it realize if it's at
>>> home or not when it wakes up and mount anything appropriate. Maybe
>>> based on the ip address that it gets, based on location.
>>>
>>> Am I doing this the hard way? How do others manage network shares
>>> with their portables? I've tried asking Google, but I haven't had
>>> much luck. Any suggestions?
>>
>> Depending on the distro you are using there may be scripts that run
>> or can be run on sleep and wake that you could add your unmount or
>> mount commands to. The unmount would probably be pretty easy, the
>> logic to check for location on wake may be a little harder, but you
>> could just put the mount command in and let it fail if the NFS server
>> isn't available. Another option would be to switch from NFS to samba
>> which is deals with loosing connections much better than NFS. The
>> samba option may be easier than trying to figure if your distro
>> supports or has sleep and wake scripts and then getting the unmount
>> and mount to work, it's the route I would take.
>>
>> Brett
>>
>> >
>>
>
>
> what about adding the "intr" option to the nfs mount?
>
>
> according to :
> http://tldp.org/LDP/nag2/x-087-2-nfs.mountd.html
> "intr : Allow signals to interrupt an NFS call. Useful for aborting
> when the server doesn't respond."
>
>
> I use this on my nfs mounts (full opts are "hard,intr,rw" in my fstab)
>
> when I take the server down or unplug the switch, I havent gotten any
> hangs resulting from a lost mount
>
>
>
That might be just what I'm looking for. I've been using soft for a
long while, but I somehow missed intr when I was researching the
options. I first started using soft after my Slackware nfs server
died and other machines would get load average around 8 while looking
for those files. I don't know how I missed intr and opted for soft
instead.
Thanks.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"NLUG" group.
To post to this group, send email to nlug-talk@googlegroups.com
To unsubscribe from this group, send email to
nlug-talk+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nlug-talk?hl=en
-~--~~~~--~~--~--~---
