From owner-freebsd-stable Tue Sep 7 17:58: 7 1999 Delivered-To: freebsd-stable@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (Postfix) with ESMTP id 39DBD1565B for ; Tue, 7 Sep 1999 17:58:04 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.9.3/8.9.3) with ESMTP id RAA57632; Tue, 7 Sep 1999 17:56:37 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Tue, 7 Sep 1999 17:56:37 -0700 (PDT) From: Doug White To: Thomas Veldhouse Cc: freebsd-stable@FreeBSD.ORG Subject: Re: NFS problem at boot? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 30 Aug 1999, Thomas Veldhouse wrote: > Yesterday, I downloaded the snaptshot, 0829, for 3.2-STABLE and I have > noticed what appears to me to be a bug. I have not been able to track > down the cause. During installation, I chose the option to set up my > machine as a NFS Server. I added the following line to my /etc/exports > file: > > /usr/src -alldirs 192.168.0.3 > > I was hoping to make my src available to another machine I am planning on > upgrading. The other machine is too slow to compile the kernel, so I want > to install it via NFS from the fast machine. > > Anyway, the machine I just installed the snapshot on gives me an error on > boot up after a long pause when trying to load rpc.statd. The error > (sorry, I am paraphrasing a bit) says that nfsd failed to register udp > with portmap. Well, I made sure portmap was running. I also tried > removing the -u option from the nfsd options, but then I get the same > error with tcp. I never had this problem under 3.1 (or perhaps even > 3.2-RELEASE), so something has gone sour. Did you turn NFSd on? Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message