From mboxrd@z Thu Jan 1 00:00:00 1970 From: "G. Allen Morris III" Subject: statd -o change Date: Fri, 4 Mar 2005 10:02:58 -0500 Message-ID: <20050304150258.GA31879@gam3.net> References: <20050227192113.GA5778@localhost.localdomain> <1109787034.12460.7.camel@lade.trondhjem.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: nhorman@redhat.com, nfs@lists.sourceforge.net Received: from sc8-sf-mx1-b.sourceforge.net ([10.3.1.11] helo=sc8-sf-mx1.sourceforge.net) by sc8-sf-list2.sourceforge.net with esmtp (Exim 4.30) id 1D7EKc-0005yD-Um for nfs@lists.sourceforge.net; Fri, 04 Mar 2005 07:03:10 -0800 Received: from mta13.mail.adelphia.net ([68.168.78.44] helo=mta13.adelphia.net) by sc8-sf-mx1.sourceforge.net with esmtp (Exim 4.41) id 1D7EKb-00042e-4P for nfs@lists.sourceforge.net; Fri, 04 Mar 2005 07:03:10 -0800 To: Trond Myklebust In-Reply-To: <1109787034.12460.7.camel@lade.trondhjem.org> Sender: nfs-admin@lists.sourceforge.net Errors-To: nfs-admin@lists.sourceforge.net List-Unsubscribe: , List-Id: Discussion of NFS under Linux development, interoperability, and testing. List-Post: List-Help: List-Subscribe: , List-Archive: Trond, I would think that statd should fail if the outgoing port can't be bound to. The main reason to bind to a particular outgoing port is because of a firewall. If the is the reasond the statd is not going to work on if it uses a random port. Allen ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ NFS maillist - NFS@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs