RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1689467 - path_resolution on an autofs managed path resets the timer. Can this be made configurable?
Summary: path_resolution on an autofs managed path resets the timer. Can this be made ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: autofs
Version: 8.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: 8.1
Assignee: Ian Kent
QA Contact: Kun Wang
URL:
Whiteboard:
Depends On: 1640448 1653208 1672134 1681956
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-16 00:18 UTC by Ian Kent
Modified: 2020-11-14 12:52 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
By default the expire of automounted mounts depends on the last access. In very large environments this helps reduce the number of mount requests from clients which can be significant. But this can lead to mounts not being umounted when monitoring services scan directory trees containing automounts. In this case it can be beneficial to expire mounts based on whether they are actually in use (ie. contain a process working directory of open files), the so-called strict expire. To allow for this later case a master map entry mount option, strictexpire, has been added. This mount option causes mounts to expire based on whether they are actually in use. To enable this behaviour the mount option "strictexpire" needs to be added to automount master map entries and the expire behaviour will change if the kernel in use supports it.
Clone Of: 1640448
Environment:
Last Closed: 2019-11-05 22:31:56 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Patch - add strictexpire mount option (7.11 KB, patch)
2019-04-29 00:48 UTC, Ian Kent 		no flags Details | Diff
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:3639 0 None None None 2019-11-05 22:31:59 UTC

Comment 1 Ian Kent 2019-04-29 00:48:54 UTC 
Created attachment 1559722 [details]
Patch - add strictexpire mount option
Comment 5 Dave Wysochanski 2019-08-15 19:27:51 UTC 
NOTE when RHEL8.1 ships we will need to update this Kbase solution similar to what was done for RHEL7.7:
https://access.redhat.com/solutions/3225981

I tried adding it to the bug but apparently the latest bugzilla updates seem to have broken that because I always get an error now when trying to add it.
Comment 7 errata-xmlrpc 2019-11-05 22:31:56 UTC 
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-2019:3639
Note You need to log in before you can comment on or make changes to this bug.