Hi,

seems that adding "--use-weight-only" and having n weight specified for
any server does what I want (at least from what I'm seeing).


Mar 23 14:20:58 trantor08 automount[17221]: get_nfs_info: host 
nfs-server.deomain.com cost 1 weight 0
Mar 23 14:20:58 trantor08 automount[17221]: get_nfs_info: called with host 
nfs-server.deomain.com(192.168.1.27) proto 17 version 0x30
Mar 23 14:20:58 trantor08 automount[17221]: get_nfs_info: nfs v3 rpc ping time: 
0.000099
Mar 23 14:20:58 trantor08 automount[17221]: get_nfs_info: nfs v2 rpc ping time: 
0.000071
Mar 23 14:20:58 trantor08 automount[17221]: get_nfs_info: host 
nfs-server.deomain.com cost 1 weight 0
Mar 23 14:20:58 trantor08 automount[17221]: get_nfs_info: called with host 
nfs-server.deomain.com(192.168.1.18) proto 6 version 0x30
Mar 23 14:20:58 trantor08 automount[17221]: get_nfs_info: nfs v3 rpc ping time: 
0.000140
Mar 23 14:20:58 trantor08 automount[17221]: get_nfs_info: nfs v2 rpc ping time: 
0.000086
Mar 23 14:20:58 trantor08 automount[17221]: get_nfs_info: host 
nfs-server.deomain.com cost 1 weight 0
Mar 23 14:20:58 trantor08 automount[17221]: get_nfs_info: called with host 
nfs-server.deomain.com(192.168.1.18) proto 17 version 0x30
Mar 23 14:20:58 trantor08 automount[17221]: get_nfs_info: nfs v3 rpc ping time: 
0.000142
Mar 23 14:20:58 trantor08 automount[17221]: get_nfs_info: nfs v2 rpc ping time: 
0.000081
Mar 23 14:20:58 trantor08 automount[17221]: get_nfs_info: host 
nfs-server.deomain.com cost 1 weight 0
Mar 23 14:20:58 trantor08 automount[17221]: get_nfs_info: called with host 
nfs-server.deomain.com(192.168.1.28) proto 6 version 0x30
Mar 23 14:20:58 trantor08 automount[17221]: get_nfs_info: nfs v3 rpc ping time: 
0.000146
Mar 23 14:20:58 trantor08 automount[17221]: get_nfs_info: nfs v2 rpc ping time: 
0.000088
Mar 23 14:20:58 trantor08 automount[17221]: get_nfs_info: host 
nfs-server.deomain.com cost 1 weight 0
Mar 23 14:20:58 trantor08 automount[17221]: get_nfs_info: called with host 
nfs-server.deomain.com(192.168.1.28) proto 17 version 0x30
Mar 23 14:20:58 trantor08 automount[17221]: get_nfs_info: nfs v3 rpc ping time: 
0.000116
Mar 23 14:20:58 trantor08 automount[17221]: get_nfs_info: nfs v2 rpc ping time: 
0.000078
Mar 23 14:20:58 trantor08 automount[17221]: get_nfs_info: host 
nfs-server.deomain.com cost 1 weight 0
Mar 23 14:20:58 trantor08 automount[17221]: get_nfs_info: called with host 
nfs-server.deomain.com(192.168.1.10) proto 6 version 0x30
Mar 23 14:20:58 trantor08 automount[17221]: get_nfs_info: nfs v3 rpc ping time: 
0.000096
Mar 23 14:20:58 trantor08 automount[17221]: get_nfs_info: nfs v2 rpc ping time: 
0.000076
Mar 23 14:20:58 trantor08 automount[17221]: get_nfs_info: host 
nfs-server.deomain.com cost 1 weight 0
Mar 23 14:20:58 trantor08 automount[17221]: get_nfs_info: called with host 
nfs-server.deomain.com(192.168.1.10) proto 17 version 0x30
Mar 23 14:20:58 trantor08 automount[17221]: get_nfs_info: nfs v3 rpc ping time: 
0.000272
Mar 23 14:20:58 trantor08 automount[17221]: get_nfs_info: nfs v2 rpc ping time: 
0.000308
Mar 23 14:20:58 trantor08 automount[17221]: get_nfs_info: host 
nfs-server.deomain.com cost 1 weight 0
Mar 23 14:20:58 trantor08 automount[17221]: get_nfs_info: called with host 
nfs-server.deomain.com(192.168.1.43) proto 6 version 0x30
Mar 23 14:20:58 trantor08 automount[17221]: get_nfs_info: nfs v3 rpc ping time: 
0.000114
Mar 23 14:20:58 trantor08 automount[17221]: get_nfs_info: nfs v2 rpc ping time: 
0.000067
Mar 23 14:20:58 trantor08 automount[17221]: get_nfs_info: host 
nfs-server.deomain.com cost 1 weight 0
Mar 23 14:20:58 trantor08 automount[17221]: get_nfs_info: called with host 
nfs-server.deomain.com(192.168.1.43) proto 17 version 0x30
Mar 23 14:20:58 trantor08 automount[17221]: get_nfs_info: nfs v3 rpc ping time: 
0.000083
Mar 23 14:20:58 trantor08 automount[17221]: get_nfs_info: nfs v2 rpc ping time: 
0.000074
Mar 23 14:20:58 trantor08 automount[17221]: get_nfs_info: host 
nfs-server.deomain.com cost 1 weight 0
Mar 23 14:20:58 trantor08 automount[17221]: get_nfs_info: called with host 
nfs-server.deomain.com(192.168.1.49) proto 6 version 0x30




In any case I still have the same qeustions :-)

Cheers,
Arnau

Reply via email to