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>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170227074340.236ce0b9>