From owner-freebsd-hackers@freebsd.org  Mon Feb 27 06:43:46 2017
Return-Path: <owner-freebsd-hackers@freebsd.org>
Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 79D8DCEF54B
 for <freebsd-hackers@mailman.ysv.freebsd.org>;
 Mon, 27 Feb 2017 06:43:46 +0000 (UTC)
 (envelope-from freebsd-hackers@dino.sk)
Received: from mailhost.netlabit.sk (mailhost.netlabit.sk [84.245.65.72])
 (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id E70546E1
 for <freebsd-hackers@freebsd.org>; Mon, 27 Feb 2017 06:43:45 +0000 (UTC)
 (envelope-from freebsd-hackers@dino.sk)
Received: from zeta.dino.sk (fw3.dino.sk [84.245.95.254]) (AUTH: LOGIN milan)
 by mailhost.netlabit.sk with ESMTPA; Mon, 27 Feb 2017 07:43:40 +0100
 id 00F4BD53.58B3CA9C.00001029
Date: Mon, 27 Feb 2017 07:43:40 +0100
From: Milan Obuch <freebsd-hackers@dino.sk>
To: Rick Macklem <rmacklem@uoguelph.ca>
Cc: Daniel Braniss <danny@cs.huji.ac.il>,
 Daniel Shahaf <danielsh@apache.org>, freebsd-hackers@freebsd.org
Subject: Re: svn over nfs - was kern.ostype - where gets its value?
Message-ID: <20170227074340.236ce0b9@zeta.dino.sk>
In-Reply-To: <YTXPR01MB01893C81CBC64D9194AD8BC5DD540@YTXPR01MB0189.CANPRD01.PROD.OUTLOOK.COM>
References: <20170226132548.69223dcd@zeta.dino.sk>
 <20170226124742.GA10967@fujitsu.shahaf.local2>
 <20170226140645.5d3ad3c1@zeta.dino.sk>
 <BCF9D145-BFE2-42CF-A03F-8173F6FC742C@cs.huji.ac.il>
 <20170226154325.48cab161@zeta.dino.sk>
 <YTXPR01MB01893C81CBC64D9194AD8BC5DD540@YTXPR01MB0189.CANPRD01.PROD.OUTLOOK.COM>
X-Mailer: Claws Mail 3.14.1 (GTK+ 2.24.29; i386-portbld-freebsd10.3)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
 <freebsd-hackers.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-hackers>, 
 <mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers/>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-hackers>, 
 <mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Feb 2017 06:43:46 -0000

On Sun, 26 Feb 2017 21:57:00 +0000
Rick Macklem <rmacklem@uoguelph.ca> wrote:

> Milan Obuch wrote:
> [more snipped]
> > > How could I find whether locking is supported/make sure it is?  
> > you need to run rpc_lockd on both server & client
> > (rpc_lockd_enable=yes in rc.conf) probably also rpc_statd too.
> >  
> You could try the "nolockd" mount option instead. It allows for
> the locking to be done locally within the client.
> 
> The only time this option isn't appropriate is if other clients need
> to see the locks. For that, I recommend using NFSv4.
> 
> rick
>

Thanks, this works! Normally, for /usr/src (and partially
for /usr/ports) read only access is enough, I see no need for locking
at all, in any case, first action is 'svn update' from svn server (here
both read and write are necessary), followed by 'make buildworld' et all
on any nfs client device (only read is necessary). No potential
conflict here. With proper setting in /etc/make.conf, similar use case
could be achieved with /usr/ports tree... so I am glad it works.

Regards,
Milan