From owner-freebsd-current  Sun Jan 31 17:25:22 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id RAA26964
          for freebsd-current-outgoing; Sun, 31 Jan 1999 17:25:22 -0800 (PST)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from fep1-orange.clear.net.nz (fep1-orange.clear.net.nz [203.97.32.1])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA26952
          for <current@FreeBSD.ORG>; Sun, 31 Jan 1999 17:25:16 -0800 (PST)
          (envelope-from jabley@buddha.clear.net.nz)
Received: from buddha.clear.net.nz (buddha.clear.net.nz [192.168.24.106]) by fep1-orange.clear.net.nz (1.5/1.11) with ESMTP id OAA02348; Mon, 1 Feb 1999 14:25:07 +1300 (NZDT)
Received: (from jabley@localhost)
	by buddha.clear.net.nz (8.9.2/8.9.1) id OAA50584;
	Mon, 1 Feb 1999 14:25:07 +1300 (NZDT)
	(envelope-from jabley)
Date: Mon, 1 Feb 1999 14:25:03 +1300
From: Joe Abley <jabley@clear.co.nz>
To: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Cc: obrien@NUXI.com, current@FreeBSD.ORG, jabley@clear.co.nz
Subject: Re: Even more interesting NFS problems..
Message-ID: <19990201142503.B50525@clear.co.nz>
References: <19990131024914.C67786@relay.nuxi.com> <1374.917785105@zippy.cdrom.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.1i
In-Reply-To: <1374.917785105@zippy.cdrom.com>; from Jordan K. Hubbard on Sun, Jan 31, 1999 at 04:18:25AM -0800
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I've been using amd on bleeding-edge current for the past year or so with
no problems - the servers in my case are Solaris 2.5.1 boxes.

I remember becoming extremely confused when I configured my first amd map
file, since there was no coherent documentation to be found at the time, but
I ended up with this (and have kept it ever since):

  % grep amd /etc/rc.conf
  amd_enable="YES"		# Run amd service with $amd_flags (or NO).
  amd_flags="-a /a -c 1800 -k i386 -d clear.net.nz -l syslog /home /etc/amd.home.map /net /etc/amd.net.map"
  amd_map_program="NO"		# Can be set to "ypcat -k amd.master"
  %
  % cat /etc/amd.home.map
  # auto-mount home directories
  /defaults	type:=nfs;rfs=/export/${path};rhost:=oms
  jabley		rhost:=intdev
  *		opts:=rw,resvport
  %
  % cat /etc/amd.net.map
  # automount /net hierarchies
  /defaults		opts:=rw,grpid,resvport,nosuid
  buddha			type:=link;fs=/
  *			type:=host;rhost:=${key}
  
buddha is the local machine; intdev is where my home directory happens to
be (everybody else's is mounted off oms).

Never had a problem with it. Just to confirm that amd is not hideously
broken beyond the point where _some_ people can use it just fine.


Joe


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