>Date: Mon, 1 Feb 1999 14:25:03 +1300
>From: Joe Abley <jab...@clear.co.nz>
>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.
Likewise, though nearly all of our NFS activity is among FreeBSD boxen.
And we use NIS for the amd maps:
pau-amma[1] grep amd /etc/rc.conf
amd_enable="YES" # Run amd service with $amd_flags (or NO).
amd_flags="-nr -k i386 -l syslog -x all"
amd_map_program="ypcat -k amd.master"
Such as
pau-amma[2] ypcat -k amd.n
*
host!=${key};os==freebsd3;type:=host;fs:=${autodir}/${rhost}/root;opts:=vers=2,proto=udp,nosuid,grpid,soft,intr
host!=${key};os!=freebsd3;type:=host;fs:=${autodir}/${rhost}/root;opts:=nfsv2,noconn,nosuid,grpid,soft,intr
host==${key};type:=link;fs:=/
/defaults rhost:=${key}
Urrgh... That's a little ugly. Reformatted:
* host!=${key};os==freebsd3;type:=host;fs:=${autodir}/${rhost}/root;\
opts:=vers=2,proto=udp,nosuid,grpid,soft,intr
host!=${key};os!=freebsd3;type:=host;fs:=${autodir}/${rhost}/root;\
opts:=nfsv2,noconn,nosuid,grpid,soft,intr
host==${key};type:=link;fs:=/
/defaults rhost:=${key}
Basically: if this is the host in question, don't even use NFS; let amd
simulate a symlink. Otherwise, use the release-specific incantation to
force the use of NFS V2/UDP.
And "amd.n" is the map we use for the equivalent of the Sun automounter
"/hosts" map.
Putting the "release-specific incantation" stuff in there managed to
shut am-util's whining about "nfsv2" up.
And using the rel. 1.2 of contrib/amd/libamu/mount_fs.c made it quit
spitting out silly messages about "noconn". (Yes, I also sent a copy of
that patch to the am-utils maintainer.)
david
--
David Wolfskill UNIX System Administrator
d...@whistle.com voice: (650) 577-7158 pager: (650) 371-4621
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
