Hi, Rob:
It's a Unix thing. there are no such "locks" in the Unix file
system(s), per se ...
NFS was designed originally for the BSD (Berkley System Distribution) of
Unix ... (aka. "Berzerkley" Unix...), specifically, by Sun Microsystems,
for their Solaris Unix OS, which was, I believe, based on BSD originally.
Try this test scenario:
1. from CLIENT-A, issue EDTF on that file.
2. from CLIENT-B, issue EDTF on that same file ...
NFS should not pevent you from doing so. :-o
3. save from CLIENT-A.
4. now save from CLIENT-B.
5. now investigate what happened ... :-(
Best to only allow updating those files from jobs running on the SERVER
(NFS host).
SUMMARY
If you are going to use NFS, "best practice" is to use it to share
"read-only" copies of files on the NFS server ... if you are going to
allow updating of those files, well, ... good luck/.... :-//
Hope that helps,
Mark S. Wtaerbury
> On 1/28/2013 9:31 AM, rob@xxxxxxxxx wrote:
Verified that running EDTF on CLIENT on a file served by SERVER does not
update the lock status of it on SERVER by running iNav and checking it's
usage. However, running EDTF locally on SERVER does.
Wouldn't that be a bug?
Rob Berendt
