>>>>> " " == apark <[EMAIL PROTECTED]> writes:
> Hi, Recently upgraded to 2.2.19, along with new
> nfs-utils(0.3.1). But I have a program that requires a
> exclusive write lock on a NFSed directory. When I was using
> 2.2.17 all was ok, but now it returns ENOLCK. Does anybody
> else have the same problem? Thanks
Hi,
You are probably failing to run the statd daemon or you may have set
up over-restrictive /etc/hosts.(allow|deny).
See the latest NFS-HOWTO for a full description on how to set up
locking.
Cheers,
Trond
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
