Date: Fri, 15 Jan 1999 07:32:10 -0800 (PST) From: Chris Timmons <skynyrd@opus.cts.cwu.edu> To: Satoshi Asami <asami@FreeBSD.ORG> Cc: freebsd-current@FreeBSD.ORG Subject: Re: NFS woes: getting worse? Message-ID: <Pine.BSF.3.96.990115072729.17168B-100000@opus.cts.cwu.edu> In-Reply-To: <199901150811.AAA25308@silvia.hip.berkeley.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <skynyrd@opus.cts.cwu.edu> > * > * * 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.990115072729.17168B-100000>