From owner-freebsd-stable  Mon May 19 15:41:32 1997
Return-Path: <owner-stable>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id PAA23900
          for stable-outgoing; Mon, 19 May 1997 15:41:32 -0700 (PDT)
Received: from silvia.HIP.Berkeley.EDU (ala-ca9-46.ix.netcom.com [207.93.143.110])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA23887
          for <freebsd-stable@freebsd.org>; Mon, 19 May 1997 15:41:28 -0700 (PDT)
Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.5/8.6.9) id PAA00919; Mon, 19 May 1997 15:40:35 -0700 (PDT)
Date: Mon, 19 May 1997 15:40:35 -0700 (PDT)
Message-Id: <199705192240.PAA00919@silvia.HIP.Berkeley.EDU>
To: jhay@zibbi.mikom.csir.co.za
CC: jhay@zibbi.mikom.csir.co.za, freebsd-stable@freebsd.org
In-reply-to: <199705191640.SAA05016@zibbi.mikom.csir.co.za> (message from John Hay on Mon, 19 May 1997 18:40:59 +0200 (SAT))
Subject: Re: amd and nfs v2 problems
From: asami@vader.cs.berkeley.edu (Satoshi Asami)
Sender: owner-stable@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

 * Is there someone actually using amd on 2.2.2 or is the problem just
 * with my setup?

I saw the same thing on my friend's place (two machines cross-mounted
by amd) last night.  I did a cvs update and noticed one of amd's
sources were changed, so I rebuilt amd and rebooted both machines.
The problem then went away.

Satoshi