From owner-freebsd-hackers Thu Sep 11 21:48:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA01521 for hackers-outgoing; Thu, 11 Sep 1997 21:48:05 -0700 (PDT) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA01450 for ; Thu, 11 Sep 1997 21:48:00 -0700 (PDT) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.7/8.8.5) with ESMTP id VAA13515; Thu, 11 Sep 1997 21:47:52 -0700 (PDT) Message-Id: <199709120447.VAA13515@austin.polstra.com> To: julian@whistle.com Subject: Re: AMD broken in 2.2.2? In-Reply-To: <34188660.1CFBAE39@whistle.com> References: <34188660.1CFBAE39@whistle.com> Organization: Polstra & Co., Seattle, WA Cc: hackers@freebsd.org Date: Thu, 11 Sep 1997 21:47:52 -0700 From: John Polstra Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article <34188660.1CFBAE39@whistle.com>, Julian Elischer wrote: > If I just turn on amd in rc.conf > and use the standard settings, > I get the following: > > # ls /host/phaser3/data > # tail /var/log/messages > [old stuff] > Sep 11 16:54:40 phaser3 amd.hold[4252]: NIS domain name is not set. NIS > ignored > Sep 11 16:55:36 phaser3 amd.hold[4550]: /net/phaser3/data: mount: Bad > address I think it was in fact broken in 2.2.2-RELEASE. I had the same symptoms as you. I replaced the amd executable with one from 2.2-STABLE and the problems went away. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth