Will

Does the addition of exclusive create change office behavior?

- nevermind - i misread a read of a directory as indicating read-only permissions on the underlying FS

Could this be something about 'word defaults to open files on remote servers in a protected view' https://answers.microsoft.com/en-us/msoffice/forum/all/word-for-mac-opens-docs-on-a-server-read-only-how/410df015-4b27-414e-9e0f-2a4ac233f580 ?

> There's a major issue with NLM in this context - which is that from what i can tell mount'ing of NFS (the clients in Mac and Linux at least)...

looking at the kernel handling of `locallocks` - (https://github.com/nneonneo/osx-10.9-opensource/blob/master/xnu-2422.1.72/bsd/vfs/kpi_vfs.c#L4823 may be as reasonable a place to start diving in as anywhere) it looks like the advisory locks are dealt with...

I wonder if another potential culprit could be that nfsv3 doesn't support extended file attributes. If the software is trying to make use of extended attributes, it will find that...

* when using this library in a larger program, you can connect it up to whatever logging system is in use via `SetLogger` https://github.com/willscott/go-nfs/blob/master/log.go#L61 * I think you're right that...

this should be better with #118 - it changes the default caching handler to re-use/have more stable handle behavior, which seems needed in many cases.

@brandonbloom can you check if the master / head of this repo now has reasonable behavior / does not cause the error you saw previously?

either we need to switch the validation to look at the digest header sent and confirm it against the secret token, or we need both secret and older validation tokens...