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:34:36 -0500 Message-ID: <20050304153436.GA32203@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-mx2-b.sourceforge.net ([10.3.1.12] helo=sc8-sf-mx2.sourceforge.net) by sc8-sf-list2.sourceforge.net with esmtp (Exim 4.30) id 1D7EpH-0008SY-CN for nfs@lists.sourceforge.net; Fri, 04 Mar 2005 07:34:51 -0800 Received: from mta9.adelphia.net ([68.168.78.199]) by sc8-sf-mx2.sourceforge.net with esmtp (Exim 4.41) id 1D7EpF-0005Yg-SM for nfs@lists.sourceforge.net; Fri, 04 Mar 2005 07:34:51 -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 requested outgoing port (-o) can't be bound to. The main reason to bind to a particular outgoing port is because of a firewall. If a random port is used statd will not make it through the firewall, but the log file will have to be checked to find out why statd is not working (falling back on randomly chosen port). Not starting statd seems to be the failure mode if the rpc.statd port (-p) can't be bound to. 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