Date: Sat, 30 Aug 2014 23:26:50 +0200 From: Ivan Voras <ivoras@freebsd.org> To: Rick Macklem <rmacklem@uoguelph.ca> Cc: freebsd-fs <freebsd-fs@freebsd.org>, Don Lewis <truckman@freebsd.org> Subject: Re: lockf(1) and NFS Message-ID: <CAF-QHFUsJjUnR9qSYJpymhS8JDrJ5%2B_iyx%2BcAEeoEnvKi6ooGQ@mail.gmail.com> In-Reply-To: <1588968883.30624902.1409399219119.JavaMail.root@uoguelph.ca> References: <201408300051.s7U0peLr073400@gw.catspoiler.org> <1588968883.30624902.1409399219119.JavaMail.root@uoguelph.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
On 30 August 2014 13:46, Rick Macklem <rmacklem@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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAF-QHFUsJjUnR9qSYJpymhS8JDrJ5%2B_iyx%2BcAEeoEnvKi6ooGQ>