From owner-freebsd-hackers  Wed May 29 03:37:13 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id DAA24835
          for hackers-outgoing; Wed, 29 May 1996 03:37:13 -0700 (PDT)
Received: from mail.barrnet.net (mail.barrnet.net [131.119.246.7])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id DAA24830
          for <hackers@freebsd.org>; Wed, 29 May 1996 03:37:12 -0700 (PDT)
Received: from Root.COM (implode.Root.COM [198.145.90.17]) by mail.barrnet.net (8.7.5/MAIL-RELAY-LEN) with ESMTP id DAA12048 for <hackers@freebsd.org>; Wed, 29 May 1996 03:37:11 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by Root.COM (8.7.5/8.6.5) with SMTP id DAA01154 for <hackers@freebsd.org>; Wed, 29 May 1996 03:33:22 -0700 (PDT)
Message-Id: <199605291033.DAA01154@Root.COM>
X-Authentication-Warning: implode.Root.COM: Host localhost [127.0.0.1] didn't use HELO protocol
To: hackers@freebsd.org
Subject: stange behavior with amd
From: David Greenman <davidg@Root.COM>
Reply-To: davidg@Root.COM
Date: Wed, 29 May 1996 03:33:22 -0700
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

   I'm having an impossible time fixing amd on a Walnut Creek machine. It
broke last week for unknown reasons and for the life of me, I can't figure
out why. The symptom is that the auto-mount just hangs. I can manually NFS
mount the remote system just fine and the amd configuration is identical
to what we're using on other WC machines (including freefall) - and they
work fine. I rebuilt the kernel (2.1-stable) and amd, but this made no
difference. I've checked everything I can think of - everything related
to DNS, permissions on various directories, etc., everything looks fine.

   amd is being started with:

amd -a /net -c 1800 -k i386 -d cdrom.com -l syslog /host /etc/amd.map

   The amd.map file contains:

/defaults       type:=host;fs:=${autodir}/${rhost};rhost:=${key}
*               opts:=rw,grpid

   Has anyone here seen this type of behavior before and perhaps have a
solution? I've spent many hours on this and I'm getting really sick of it.

-DG

David Greenman
Core-team/Principal Architect, The FreeBSD Project