Hi there;

I have two servers, separated by 3,000 miles, that share NFS mounted partitions.

Something happened a couple of days ago to cause the mounts to fail.
(I have no control over the internal corporate network that separates
the two sites.)

I finally was able to cure the problem by using the NFS proto=tcp option.

However; (there is always a however)

auto_master contains:
/remote/projects auto_submap

auto_submap file now contains;
projects -o proto=tcp FQDN:/a/projects

After adding this entry, things magically stated working again,
but (there is always a but) root gets e-mail with the following
message;

Feb 11 08:47:14 hostname automountd[171]: parse_nfs: bad entry in map
auto_submap "proto=tcp"

So, the question is:
What is the correct way to get automount to use proto=tcp?


Linolil

Linolil wrote:
> auto_master contains:
> /remote/projects auto_submap
>
> auto_submap file now contains;
> projects -o proto=tcp FQDN:/a/projects
>
> Feb 11 08:47:14 hostname automountd[171]: parse_nfs: bad entry in map
> auto_submap "proto=tcp"
>
> So, the question is:
> What is the correct way to get automount to use proto=tcp?

I believe it should be
projects -proto=tcp FQDN:/a/projects

other options would be comma separated as in
projects -ro,proto=tcp,etc FQDN:/a/projects