Date: Thu, 06 Jan 2011 00:44:48 -0800 From: perryh@pluto.rain.com To: rmacklem@uoguelph.ca Cc: marek_sal@wp.pl, freebsd-stable@freebsd.org, milu@dat.pl, jyavenard@gmail.com, jhb@freebsd.org Subject: Re: NFSv4 - how to set up at FreeBSD 8.1 ? Message-ID: <4d258100.Wu9WZrgdH2/KvDTa%perryh@pluto.rain.com> In-Reply-To: <1870282066.118978.1294234205820.JavaMail.root@erie.cs.uoguelph.ca> References: <1870282066.118978.1294234205820.JavaMail.root@erie.cs.uoguelph.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
Rick Macklem <rmacklem@uoguelph.ca> wrote: > Sun did add a separate file locking protocol called the NLM > or rpc.lockd if you prefer, but that protocol design was > fundamentally flawed imho and, as such, using it is in the > "your mileage may vary" category. I suppose it was not all that bad, considering that what it sought to accomplish is incomputable. There is simply no way for either the server or the client to distinguish between "the other end has crashed" and "there is a temporary communication failure" until the other end comes back up or communication is restored. On a good day, in a completely homogeneous environment (server and all clients running the same OS revision and patchlevel), I trust lockd about as far as I can throw 10GB of 1980's SMD disk drives :) Exporting /var/spool/mail read/write tends to ensure that good days will be rare. Been there, done that, seen the result. Never again. That's what IMAP is for.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4d258100.Wu9WZrgdH2/KvDTa%perryh>