Date: Mon, 08 Feb 2010 17:21:08 +0000 From: "O. Hartmann" <ohartman@zedat.fu-berlin.de> To: Rick Macklem <rmacklem@uoguelph.ca> Cc: freebsd-stable@freebsd.org, freebsd-questions@freebsd.org Subject: Re: NFSv4: mount -t nsf4 not the same as mount_newnfs? Message-ID: <4B704804.4030802@zedat.fu-berlin.de> In-Reply-To: <Pine.GSO.4.63.1002081001390.25952@muncher.cs.uoguelph.ca> References: <4B6FE550.9020506@zedat.fu-berlin.de> <Pine.GSO.4.63.1002081001390.25952@muncher.cs.uoguelph.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
On 02/08/10 15:08, Rick Macklem wrote: > > > On Mon, 8 Feb 2010, O. Hartmann wrote: > >> >> Mounting the filessystem via >> >> mount_newnfs host:/path /path >> > Oh, and you should set: > sysctl vfs.newnfs.locallocks_enable=0 > in the server, since I haven't fixed the local locking yet. (This implies > that apps/daemons running locally on the server won't see byte range > locks performed by NFSv4 clients.) However, byte range locking between > NFSv4 clients should work ok. > > rick > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" Interesting, I see a lot of vfs.newfs-stuff on server-side, but not this specific OID. Do I miss something here? Regards, Oliver
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4B704804.4030802>