lockf(1) and NFS

[Ivan Voras]

On 30 August 2014 13:46, Rick Macklem <rmacklem at uoguelph.ca> wrote:

> Doing locking locally within the client is still possible with the "nolockd"
> option. However, when this mount option is used all file locking,
> including POSIX byte range locks, are done locally.
>
> Linux has a similar mount option (called "nolock" I think?), but I
> don't know if Solaris has any mount option.
>
> I'm pretty sure Ivan knows about this, so I suspect he needs lockf(1)
> to work across multiple clients for his app., but don't know for sure?

Yes, I know about the mount options; actually, I found later that the
cause of my problem was not in lockf(1), so I don't actually *need*
this patch (or at least I don't need it *yet*). I wanted to have
proper locking working across machines.