svn over nfs - was kern.ostype - where gets its value?

Milan Obuch freebsd-hackers at dino.sk
Mon Feb 27 06:43:46 UTC 2017


On Sun, 26 Feb 2017 21:57:00 +0000
Rick Macklem <rmacklem at 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


More information about the freebsd-hackers mailing list