Xref: utzoo comp.unix.ultrix:7392 comp.protocols.nfs:2369 Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!spool.mu.edu!munnari.oz.au!metro!grivel!loki!mark From: mark@loki.une.oz.au (Mark Garrett) Newsgroups: comp.unix.ultrix,comp.protocols.nfs Subject: Re: nfsd 4, why, and how to tune... Message-ID: <1538@loki.une.oz.au> Date: 27 May 91 10:17:18 GMT Article-I.D.: loki.1538 References: <21936@cbmvax.commodore.com> Followup-To: comp.unix.ultrix Organization: University of NewEngland, Northern Rivers (Lismore) Lines: 15 grr@cbmvax.commodore.com (George Robbins): > In article rusty@groan.Berkeley.EDU (Rusty Wright) writes: > filesystem brings the server to it's knees, with the NFS deamons sharing > ~100% of the CPU time amongst themselves... Ouch. This happens often > enough to be a recognizable syndrome and prompts a witch hunt to find > which client is up to mischief ] I've only got ultrix to play with, and it was only last weekend that I gave NFS its first run ,exporting src from a VAX3500 to a DecSystem5400 , to find that the 3500 got a real kick in the response time with very little NFS effort. I was not impressed, believing this to be normal behavior for NFS I'm glad to hear its Ultrix (sort of). Has Ultrix 4.2 fixed this, would BSD source for NFS have the same problems ? -- Mark Garrett Internet: mark@loki.une.edu.au Phone: +61 (066) 20 3859 University of NewEngland, Northern Rivers, Lismore NSW Australia.