From: Bernd Schubert Subject: Re: RELEASE CANDIDATE - nfs-utils-1.1.0-rc1 Date: Thu, 29 Mar 2007 11:51:58 +0200 Message-ID: <200703291151.59120.bernd-schubert@gmx.de> References: <17931.15549.578071.112573@notabene.brown> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: nfs@lists.sourceforge.net 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 1HWrId-0001eL-CM for nfs@lists.sourceforge.net; Thu, 29 Mar 2007 02:52:11 -0700 Received: from mail.gmx.net ([213.165.64.20]) by mail.sourceforge.net with smtp (Exim 4.44) id 1HWrIe-0001mL-7Q for nfs@lists.sourceforge.net; Thu, 29 Mar 2007 02:52:09 -0700 In-Reply-To: <17931.15549.578071.112573@notabene.brown> 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 Thursday 29 March 2007 06:12:45 Neil Brown wrote: > I've finished fiddling with statd, and am happy with mount.nfs now, so > it must be time for the first release candidate for nfs-utils-1.1.0. > While you are working on statd, maybe you can look into a problem I recently had? After the update from Debian Sarge to Etch, the update scripts dumped the current portmapper status to read them in after the portmap restart. Well, this was an update of a chroot and the portmapper never got restartet on the server and so also the dump file wasn't deleted. The diskless clients using this chroot read in the dump file, but also couldn't delete it, since it was located in a read-only nfs-export (*). The problem was statd, the dumpfile said that statd is running on a port < 1024, but since rpc.statd as user statd is not allowed to use ports <1024, it refused to start up at all. Well, while this clearly can and should be solved by removing the stale portmapper dump file, maybe there's also a solution for rpc.statd? Thanks, Bernd PS: (*) Somewhere in /var, which will become writable after a union mount, which will be done after the start-up of portmap. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ NFS maillist - NFS@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs