lkml.org 
[lkml]   [1998]   [Dec]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: fcntl behaviour different in 2.1.129
Date
> 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/

\
 
 \ /
  Last update: 2005-03-22 13:46    [W:0.052 / U:0.416 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site