From owner-freebsd-stable  Thu Aug 12 12:46:47 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from pau-amma.whistle.com (pau-amma.whistle.com [207.76.205.64])
	by hub.freebsd.org (Postfix) with ESMTP id C3A2F1585F
	for <stable@FreeBSD.ORG>; Thu, 12 Aug 1999 12:46:44 -0700 (PDT)
	(envelope-from dhw@whistle.com)
Received: (from dhw@localhost)
	by pau-amma.whistle.com (8.9.2/8.9.2) id MAA98218;
	Thu, 12 Aug 1999 12:46:47 -0700 (PDT)
Date: Thu, 12 Aug 1999 12:46:47 -0700 (PDT)
From: David Wolfskill <dhw@whistle.com>
Message-Id: <199908121946.MAA98218@pau-amma.whistle.com>
To: imp@village.org, stable@FreeBSD.ORG
Subject: Re: Kludge-o-round for 1 3.2 STABLE NFS problem
In-Reply-To: <199908121933.NAA05527@harmony.village.org>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>Date: Thu, 12 Aug 1999 13:33:41 -0600
>From: Warner Losh <imp@village.org>

>We were having all kinds of problems using NFS on locally mounted file
>systems (that is, the client and server were on the same machine).....


I encountered similar symptoms back when I started here, at around
2.2.6-R.

My circumvention was to hack the amd maps in such a way that amd would
recognize when the client & server had the same name:

* If not, do the usual NFS stuff;

* If so, instead of providing the illusion of an NFS mount, provide the
  illusion of a symlink.


This is what allowed me to get anything at all done for the past several
months....

I *thought* I had sent a note to one of the freebsd lists about it,
including some of the stuff in the amd maps.  If it appears to be of
use, I'm certainly willing to share.

(The note to the effect that "a weird imagination is most useful to gain
full advantage of some of all the [amd] features" is well-advised.)

And of course, I freely admit that the approach merely masks the
problem.

Cheers,
david
-- 
David Wolfskill		dhw@whistle.com		UNIX System Administrator
voice: (650) 577-7158	pager: (888) 347-0197	FAX: (650) 372-5915


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message