From owner-freebsd-current  Mon Sep  9 11:22:26 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id LAA09514
          for current-outgoing; Mon, 9 Sep 1996 11:22:26 -0700 (PDT)
Received: from time.cdrom.com (time.cdrom.com [204.216.27.226])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA09508
          for <freebsd-current@freebsd.org>; Mon, 9 Sep 1996 11:22:23 -0700 (PDT)
Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with ESMTP id LAA21768; Mon, 9 Sep 1996 11:21:54 -0700 (PDT)
To: Charles Henrich <henrich@crh.cl.msu.edu>
cc: freebsd-current@freebsd.org
Subject: Re: Grrr. NFS to a Sun (Slowaris 5.5.1) 
In-reply-to: Your message of "Mon, 09 Sep 1996 14:14:35 EDT."
             <199609091814.OAA02906@crh.cl.msu.edu> 
Date: Mon, 09 Sep 1996 11:21:53 -0700
Message-ID: <21765.842293313@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

[ cut to -current; 3 groups is definite overkill, Charles! :( ]

> Its been my impression that the NFS on FreeBSD went really downhill between
> 0612 and 0801 ...  I've been having all sorts of annoying pauses and glitches
> to a RS/6000 as well, but nothing nearly as bad as to the sparc.

You'd be right in that impression - NFS clientry is now one of the
easiest way to crash yourself in -current.

> Hints anyone?

Find us an NFS guru with a little free time? :-) The #1 problem with
FreeBSD and NFS isn't a technical one, it's a personnel problem.  The
number of people who truly understand that code can literally be
counted on one hand, and all of them are in high demand. :-(

						Jordan