rpc.lockd

[omestre at freeshell.org]

 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.