From owner-freebsd-current Fri Jan 15 07:33:22 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA29200 for freebsd-current-outgoing; Fri, 15 Jan 1999 07:33:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from opus.cts.cwu.edu (opus.cts.cwu.edu [198.104.92.71]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA29192; Fri, 15 Jan 1999 07:33:20 -0800 (PST) (envelope-from skynyrd@opus.cts.cwu.edu) Received: from localhost (skynyrd@localhost) by opus.cts.cwu.edu (8.9.1/8.9.1) with SMTP id HAA17610; Fri, 15 Jan 1999 07:32:10 -0800 (PST) Date: Fri, 15 Jan 1999 07:32:10 -0800 (PST) From: Chris Timmons To: Satoshi Asami cc: freebsd-current@FreeBSD.ORG Subject: Re: NFS woes: getting worse? In-Reply-To: <199901150811.AAA25308@silvia.hip.berkeley.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Actually the good news is that the problems I see with the XFree86-contrib port are absolutely reproducible. To be sure I set the test case up on a different set of machines than the pair at home on which I first noticed it. I'll dig a little more this weekend and perhaps I can correlate my ktrace data against the tcpdump trace. -Chris On Fri, 15 Jan 1999, Satoshi Asami wrote: > * From: asami@FreeBSD.ORG (Satoshi Asami) > * > * * From: Chris Timmons > * > * * make: don't know how to make Makefiles. Stop > * > * I've seen similar things, but they went away when I reduced the load > * (other compilations in my case) on the server. How busy is your > * server? > > Forgot to mention, this happens with a read-only NFS tree too. I was > running builds on the client with a shared /usr/ports and WRKDIRPREFIX > pointing to a local directory, and the build will topple over in the > middle unable to find a Makefile on the server or something. > > That is the problem that went away with the server load. > > Satoshi > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message