From: Trond Myklebust Subject: Re: Problems with statd and lockd Date: 05 Apr 2003 13:50:29 +0200 Sender: nfs-admin@lists.sourceforge.net Message-ID: References: <20030405015638.5118fbb9.philippe.gramoulle@mmania.com> <20030405131821.595ca734.philippe.gramoulle@mmania.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: NFS Mailing List Return-path: Received: from mons.uio.no ([129.240.130.14]) by sc8-sf-list1.sourceforge.net with esmtp (Exim 3.31-VA-mm2 #1 (Debian)) id 191mBu-00007R-00 for ; Sat, 05 Apr 2003 03:50:34 -0800 To: Philippe Gramoull~ In-Reply-To: <20030405131821.595ca734.philippe.gramoulle@mmania.com> 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: >>>>> " " == Philippe Gramoull writes: > And do you have an idea of what could cause such errors ? The message just means what it says. The problem could be anything from a temporary hang of statd or the portmapper right down to a deep kernel bug. Cheers, Trond ------------------------------------------------------- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ _______________________________________________ NFS maillist - NFS@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs