On 4/24/07, Markus F.X.J. Oberhumer <email address hidden> wrote:
> Thanks for the feedback - the missing rpc.lockd on the server seems
> indeed to be the cause of the problem (but I cannot fix that machine).
>
> As a workaround adding "nolock" to the NFS mount options seems to be
> enough to make "bzr update" work again, though I'm not sure about the
> implications of that.
It might cause trouble if you tried to update the working tree
simultaneously from two nfs clients, which may be unlikely.
On 4/24/07, Markus F.X.J. Oberhumer <email address hidden> wrote:
> Thanks for the feedback - the missing rpc.lockd on the server seems
> indeed to be the cause of the problem (but I cannot fix that machine).
>
> As a workaround adding "nolock" to the NFS mount options seems to be
> enough to make "bzr update" work again, though I'm not sure about the
> implications of that.
It might cause trouble if you tried to update the working tree
simultaneously from two nfs clients, which may be unlikely.
--
Martin