Subject: amd and NFS via TCP
To: None <current-users@NetBSD.ORG>
From: Matthias Scheler <tron@lyssa.owl.de>
List: current-users
Date: 11/08/1997 17:24:51
	Hi,

I have these options in "/etc/amd/homes":

/defaults       type:=nfs;opts:=rw,intr,nosuid,nodevs,resvport,tcp

lyssa   type:=link;fs:=/home
*       rhost:=${key};rfs:=/home

This should IMHO cause "amd" to use TCP for NFS mounts. However if I access
"/homes/colwyn" from "lyssa" I can't see a connection between the two hosts:

Active Internet connections
Proto Recv-Q Send-Q  Local Address          Foreign Address        (state)
tcp        0      0  lyssa.owl.de.1050      colwyn.owl.de.nntp     ESTABLISHED
tcp        0      0  lyssa.owl.de.7100      lyssa.owl.de.1028      ESTABLISHED
tcp        0      0  lyssa.owl.de.1028      lyssa.owl.de.7100      ESTABLISHED
udp        0      0  lyssa-dfn.owl.de.ntp   *.*                   
udp        0      0  localhost.ntp          *.*                   
udp        0      0  lyssa.owl.de.ntp       *.*                   
udp        0      0  lyssa.owl.de.1035      lyssa.owl.de.1023     
udp        0      0  lyssa.owl.de.1034      lyssa.owl.de.1023     
udp        0      0  lyssa.owl.de.1033      lyssa.owl.de.1023     

If I mount a "colwyn:/home" manually with "mount_nfs -T ..." I can see
a TCP connection. Has "amd" a bug or is there a configuration error?

-- 
Matthias Scheler                                http://home.owl.de/~tron