I've been using amd (the automounter, not the chip company) host maps
for many years.  It is pretty handy for doing quick checks of some
other local system's fs without logging in there.

With the most recent resync to -current (right after the new resolver
patches from ISC) I noticed that amd's host maps don't work anymore.
The rest of amd seems to work just fine, but when I mount a host map I
get long delay and a "mount failed" message from both amd and mountd.

Nov 14 11:43:22 capsicum amd[5384]: mountd rpc failed: RPC: Unable to receive
Nov 14 11:43:22 capsicum amd[5384]: mountd rpc failed: RPC: Unable to receive
Nov 14 11:43:22 capsicum amd[176]: Process 5384 exited with signal 13
Nov 14 11:43:22 capsicum amd[176]: mount for /n/capsicum got signal 13
Nov 14 11:43:30 capsicum amd[5396]: mountd rpc failed: RPC: Unable to receive
Nov 14 11:43:30 capsicum amd[5396]: mountd rpc failed: RPC: Unable to receive
Nov 14 11:43:30 capsicum amd[176]: Process 5396 exited with signal 13
Nov 14 11:43:30 capsicum amd[176]: mount for /n/capsicum.wsrcc.com got signal 13

Whatever it is that caused this happened since this last Saturday.
Any one else seeing this lossage?


/etc/amd.conf:

[ /n ]
map_name =		/etc/amd/amd-n

/etc/amd/amd-n:

/defaults	opts:=intr,proto=udp;fs:=${autodir}/${rhost};type:=host;rhost:=${key}
*		;


-wolfgang
-- 
We are from the U.N. and we are here to help you.

spider food: http://www.wsrcc.com/baddream/usenet/
(NOTE: The email address above is valid.  Edit it at your own peril.)