Date: Tue, 29 Apr 2003 17:15:23 -0300 From: omestre@freeshell.org To: Dan Nelson <dnelson@allantgroup.com> Cc: freebsd-hackers@freebsd.org Subject: Re: rpc.lockd Message-ID: <20030429201528.B8741107C3@ws-tor-0004.procergs> In-Reply-To: Message from Dan Nelson <dnelson@allantgroup.com> <20030429195431.GA22259@dan.emsphone.com> References: <20030429160500.E514F107C1@ws-tor-0004.procergs> <20030429195431.GA22259@dan.emsphone.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Thanks for your answer. But, if the FreeBSD 4.x do not "lock" anything, how can i reproduce it in FreeBSD 5.0? It is not just "kill" rpc.lockd, because in FreeBSD 4.x, the programs do not know that the locks have failed. (Sorry by the english). What i want to say is: "The FreeBSD 4.x knows how to mask this situation" (very well) :) Now, in FreeBSD 5.0, after two or three days with the programs runnig, the flocks procedures returns (with sucess status). Maybe, the FreeBSD 5.0 change your behavior after some "big timeout". And if i "kill" the rpc.lockd, the flocks calls will return error, and the programs will fail. Thanks again.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030429201528.B8741107C3>