*autofs* now supports the browse options of `amd` format maps
The browse functionality of sun format maps makes available automount points visible in directory listings of mounted automount-managed mounts and is now also available for *autofs* `amd` format maps.
You can now add mount point sections to the *autofs* configuration for `amd` format mounts, in the same way automount points are configured in `amd`, without the need to also add a corresponding entry to the master map. As a result, you can avoid having incompatible master map entries in the *autofs* master map within shared multi-vendor environments.
The "browsable_dirs" option can be used in either the *autofs* `[ amd ]` configuration section, or following `amd` mount point sections. The "browsable" and "utimeout" map options of amd type "auto" map entries can also be used.
Note that the "browsable_dirs" option can be set only to `yes` or `no`.

Description of problem:
We've discussed this with Ian, and the work's already in progress, but we wanted to formalize a request:
<snip>
Even though I don't yet have an RFE for this I have done some preliminary
evaluation of the request. Unfortunately for me the way I would like to do it
will add an unacceptable amount of complexity for insufficient benefit.
That means 2 things.
First, I'll need to do this within the existing browse framework in autofs.
While not ideal from my POV I don't have any choice and initial investigation
indicates the change is fairly straight forward doing it within the existing
browse framework.
Second, I will not be able to implement the amd "fullybrowsable" option for amd
format maps in autofs for the foreseeable future. AFAICS that option has limited
use apart from perhaps amd map debugging, also Richard doesn't need this
functionality, so that shouldn't be a problem.
Being that it looked fairly straight forward the investigation resulted in an
initial partial implementation
...
I have a start to that already but considering your environment I see another
problem that I'll need to fix. I'm thinking about how to do that as well as
contributing to the autofs discussion.
It will be necessary to check that the amd map format support will function
acceptably without the additional fix.
</snip>
This will require implementation and client validation for their map setup.
Version-Release number of selected component (if applicable):
RHEL7 autofs
Additional info:
This request came out of a discussion with Ian Kent and the client, so there's a bit of history on it.

An initial test package with the above changes has been built.
It is located at:
http://people.redhat.com/ikent/autofs-5.0.7-56.bz1367576.2.el7/
We need to test there are not side effects of this change and
that the change works ok in the customer environment since the
scale of the customer environment is large.
I can help QE with test development for verification of the
required functionality.

(In reply to Frank Hirtz from comment #0)
> ...
> I have a start to that already but considering your environment I see another
> problem that I'll need to fix. I'm thinking about how to do that as well as
> contributing to the autofs discussion.
The problem that I was referring to above is related to the
frequent map reuse that is common in amd map configurations.
Given the size of the maps that will be used here the lack
of map reuse would have been a significant problem but I
believe it is addressed by the patch that adds reference
counting to the top level map source structure.
We will need to see if this is sufficient and watch out for
side effects of this particular change.

An updated test package with the above changes has been built.
It is located at:
http://people.redhat.com/ikent/autofs-5.0.7-56.bz1367576.3.el7/
This package adds the ability of autofs to use top level amd
mount sections of the autofs configuration instead of requiring
an additional master map entry.
Please give this a try and let us know how it goes.

An updated test package with the above changes has been built.
It is located at:
http://people.redhat.com/ikent/autofs-5.0.7-56.bz1367576.4.el7/
This package adds a check for amd section mounts that conflict
with entries in the master map and includes a couple of other
minor updates to existing patches.
It would be good if this package could be tested, I need to know
if this functions in the customer environment and to find out
what else I need to fix.

Created attachment 1266812[details]
Patch - use autofs_point to store expire timeout where possibe
Almost missed this patch which was partly completed.
It is needed to properly support the "utimeout" option of amd
type "auto" submounts.

Created attachment 1273487[details]
Patch - fix invalid reference in remount_active_mount()
Fix a mistake found in testing when getting the expire timeout at startup when re-connecting to existing mounts.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2017:2213

Note

You need to
log in
before you can comment on or make changes to this bug.