From: Trond Myklebust Subject: Re: Status of mount.nfs Date: Tue, 31 Jul 2007 14:30:27 -0400 Message-ID: <1185906627.6700.30.camel@localhost> References: <20070708191640.GA13962@uio.no> <18065.43199.104020.412029@notabene.brown> <20070715083114.GB4158@uio.no> <18074.50730.591965.39211@notabene.brown> <20070716092047.GA10353@uio.no> <18075.17719.855332.259470@notabene.brown> <20070722191733.GA31501@uio.no> <46A52816.6050500@oracle.com> <20070724172451.GA14026@uio.no> <46A7A5F8.4040204@oracle.com> <46A897CD.50201@RedHat.com> <46A96032.7080503@oracle.com> <46AA089E.50503@RedHat.com> <1185551769.6586.28.camel@localhost> <46AA1A70.5010705@RedHat.com> <1185553679.6586.34.camel@localhost> <46AA2642.60505@RedHat.com> <1185556406.6586.45.camel@localhost> <46AB3BE9.1060903@RedHat.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Cc: nfs@lists.sourceforge.net To: Steve Dickson Return-path: Received: from sc8-sf-mx2-b.sourceforge.net ([10.3.1.92] helo=mail.sourceforge.net) by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43) id 1IFwUP-0006vS-T5 for nfs@lists.sourceforge.net; Tue, 31 Jul 2007 11:30:38 -0700 Received: from pat.uio.no ([129.240.10.15]) by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.44) id 1IFwUR-0005LI-Be for nfs@lists.sourceforge.net; Tue, 31 Jul 2007 11:30:41 -0700 In-Reply-To: <46AB3BE9.1060903@RedHat.com> List-Id: "Discussion of NFS under Linux development, interoperability, and testing." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: nfs-bounces@lists.sourceforge.net Errors-To: nfs-bounces@lists.sourceforge.net On Sat, 2007-07-28 at 08:51 -0400, Steve Dickson wrote: > Trond Myklebust wrote: > > On Fri, 2007-07-27 at 13:07 -0400, Steve Dickson wrote: > > > >> After how long of a wait? If all the timeouts are controllable then > >> I agrees, but if we have to wait undefined-able amount of time for > >> every RPC retransmit, then I think we should do a ping... > > > > You should be able to set the timeout either on a per-RPC call basis by > > using clnt_call(), or by changing the default timeout on the CLIENT > > object using clnt_control() (man 3 rpc). > True... but I was thinking of when clnt_cnt() call pmap_getport() > which does not take a timeout value... In that case you are > stuck with a 60 sec hard coded timeout, regardless of the time out > you pass in... In the version of mount.nfs from the linux-nfs.org git tree, we call our own private implementation of pmap_getport() instead of the one from glibc. Cheers Trond ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ NFS maillist - NFS@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs