From: Trond Myklebust Subject: Re: Stale fcntl lock never released Date: 24 Jun 2003 21:02:10 +0200 Sender: nfs-admin@lists.sourceforge.net Message-ID: References: <20030623221405.GA4320@async.com.br> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: NFS@lists.sourceforge.net, Guilherme Salgado Return-path: To: Christian Reis In-Reply-To: <20030623221405.GA4320@async.com.br> Errors-To: nfs-admin@lists.sourceforge.net List-Help: List-Post: List-Subscribe: , List-Id: Discussion of NFS under Linux development, interoperability, and testing. List-Unsubscribe: , List-Archive: >>>>> " " == Christian Reis writes: > (Trond, do any of the lockd patches in > http://www.fys.uio.no/~trondmy/src/2.4.21/ fix something like > this?) No. This is what rpc.statd is supposed to do. When a client reboots, it is supposed to notify the server that it should remove all locks belonging to that client. Cheers, Trond ------------------------------------------------------- This SF.Net email is sponsored by: INetU Attention Web Developers & Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php _______________________________________________ NFS maillist - NFS@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs