On 21.07.12 12:51, Gene Heskett wrote:
> On Saturday 21 July 2012 12:14:51 Erik Christiansen did opine:
> > To make sure we only have to debug nfs, what about trying in
> > /etc/exports:
> >
> > /my/shared/filesystem 192.168.71.0/24(rw)
> >
> I just changed it to this style on lathe, and it works, but shouldn't I
> have a ,sync after the rw?
OK, then that's not only a fix, but is more robust, since it doesn't
rely on DNS being and staying good.
You can put the "sync" in, and it is probably good form. However:
"In releases of nfs-utils up to and including 1.0.0, this option was the
default. In all releases after 1.0.0, sync is the default, and async must
be explicitly requested if needed. To help make system administrators
aware of this change, 'exportfs' will issue a warning if neither sync nor async
is specified."
So if a "sudo exportfs -r" does issue the warning, then "sync" ought to
be optional, due to the default behaviour.
(Yeah, I know, it's cheap insurance to just chuck it in.)
...
> That seems to be working on lathe. So I changed the shop machines export
> file to hard address, and left the ,sync option in, restarted its nfs-
> kernel-server, and now its working from a cli at least. and so is mc
> although I haven't tried to copy anything yet.
Now that's good to hear. While fixing up DNS could be an interesting
exercise, that doesn't make any swarf, or empty out the aircon drip tray,
I figure.
Erik
--
Price's Advice:
It's all a game -- play it to have fun.
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Emc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-users
