From owner-freebsd-fs@FreeBSD.ORG  Sat Aug 30 21:27:34 2014
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: freebsd-fs@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 40E439C;
 Sat, 30 Aug 2014 21:27:34 +0000 (UTC)
Received: from mail-lb0-x230.google.com (mail-lb0-x230.google.com
 [IPv6:2a00:1450:4010:c04::230])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 949B51BE6;
 Sat, 30 Aug 2014 21:27:33 +0000 (UTC)
Received: by mail-lb0-f176.google.com with SMTP id s7so4223015lbd.35
 for <multiple recipients>; Sat, 30 Aug 2014 14:27:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:sender:in-reply-to:references:from:date:message-id
 :subject:to:cc:content-type;
 bh=JFSbSryLXBshj7XFrtDC3MlB1qGQD7GOudn70bZOsEg=;
 b=t3JEqQ2rltDT1jHqAgi3K5hI0yq7wSiQoHqjFHEVc85rGXhEPauF46yiLCPXjANWi8
 dWrAu0MgQy+dXF4DDgws4/MY34HhxlUrrU/vsd2Gxet9497R47CrrvrxYuIiyWxgUAjF
 LL4Ik39emCgEUcCgPVJ1i2sERScI6CWFz0WoCEgtcCPx8bdcce+PHRqQarO6tmpsm4Jd
 Qt5qlmKKbgonjxsRWvPOmx22HuHkindxE40a5fEF6XIvzZo1g8rhZcaY2ujz14+kMmyD
 NicTyWe93kNBDNiBYYRMrudquzS6WU7YewnZ96AHr3EBsfNE3lPP0ezUk4i5DzA2LwBv
 eHLg==
X-Received: by 10.153.5.38 with SMTP id cj6mr19267007lad.34.1409434051067;
 Sat, 30 Aug 2014 14:27:31 -0700 (PDT)
MIME-Version: 1.0
Sender: ivoras@gmail.com
Received: by 10.25.149.205 with HTTP; Sat, 30 Aug 2014 14:26:50 -0700 (PDT)
In-Reply-To: <1588968883.30624902.1409399219119.JavaMail.root@uoguelph.ca>
References: <201408300051.s7U0peLr073400@gw.catspoiler.org>
 <1588968883.30624902.1409399219119.JavaMail.root@uoguelph.ca>
From: Ivan Voras <ivoras@freebsd.org>
Date: Sat, 30 Aug 2014 23:26:50 +0200
X-Google-Sender-Auth: iLr3yNoCAbxFlJnVDIZvkyj6KE0
Message-ID: <CAF-QHFUsJjUnR9qSYJpymhS8JDrJ5+_iyx+cAEeoEnvKi6ooGQ@mail.gmail.com>
Subject: Re: lockf(1) and NFS
To: Rick Macklem <rmacklem@uoguelph.ca>
Content-Type: text/plain; charset=UTF-8
Cc: freebsd-fs <freebsd-fs@freebsd.org>, Don Lewis <truckman@freebsd.org>
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 30 Aug 2014 21:27:34 -0000

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.