From owner-freebsd-current Wed Jan 13 02:01:51 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA26847 for freebsd-current-outgoing; Wed, 13 Jan 1999 02:01:51 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA26829 for ; Wed, 13 Jan 1999 02:01:47 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 2.10 #1) id 100N6N-000CqR-00; Wed, 13 Jan 1999 12:00:39 +0200 From: Sheldon Hearn To: dan@math.berkeley.edu (Dan Strick) cc: current@FreeBSD.ORG Subject: Re: amd: noconn option exists... In-reply-to: Your message of "Tue, 12 Jan 1999 18:44:17 PST." <199901130244.SAA16073@math.berkeley.edu> Date: Wed, 13 Jan 1999 12:00:39 +0200 Message-ID: <49378.916221639@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 12 Jan 1999 18:44:17 PST, Dan Strick wrote: > Then some of my remote mounts started hanging. Then I changed > my default amd mounting option from "noconn" to "conn". > That seemed to fix everything. Hi Dan, Thanks for taking a crack at explaining this. I found the noconn option mentioned in the AMD Reference Manual (/usr/share/info/amdref.info.gz), which led me to expect the option to appear in /etc/amd.map. I can't find "noconn" _anywhere_ in my /etc/tree, so I'm a little confused as to where amd is picking this up. Clues? Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message