Re: fcntl behaviour different in 2.1.129

Alan Cox (alan@lxorguk.ukuu.org.uk)
Sat, 12 Dec 1998 18:10:39 +0000 (GMT)


> The most common cause for this error then is when you are not running the
> lockd daemon from the linux-nfs package/or the remote host is not running
> a lockd.
>
> 2.0 did all NFS locking local, in 2.1 F_SETLK tries remote locking. If you
> only want local locking convert to lockf().

Its looking like having 2.2 support a "lock=local" option on NFS to turn
off these 'problems' might be sensible ?

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/