From owner-freebsd-hackers Wed May 29 12:11:30 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA26405 for hackers-outgoing; Wed, 29 May 1996 12:11:30 -0700 (PDT) Received: from Root.COM (implode.Root.COM [198.145.90.17]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA26398 for ; Wed, 29 May 1996 12:11:27 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by Root.COM (8.7.5/8.6.5) with SMTP id MAA02095; Wed, 29 May 1996 12:11:26 -0700 (PDT) Message-Id: <199605291911.MAA02095@Root.COM> X-Authentication-Warning: implode.Root.COM: Host localhost [127.0.0.1] didn't use HELO protocol To: "Ron G. Minnich" cc: hackers@freebsd.org Subject: Re: stange behavior with amd In-reply-to: Your message of "Wed, 29 May 1996 08:00:56 EDT." From: David Greenman Reply-To: davidg@Root.COM Date: Wed, 29 May 1996 12:11:26 -0700 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >similar to problems i have seen here. hangs and/or fails. What i see via >snoop is that amd sends out the NFS NULL call and the reply just gets >dropped. Then amd tries again, and again, and again ... That's exactly what I'm seeing here. It _was_ working, however. I don't understand what has change to break it all of a sudden. >I have not had time to fix it. Seems like it is probably a bug in amd, >though, ... arg. Hmmm. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project