Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 190877

Summary: Autofs does not allow a file map to include a nis map of the same name
Product: Red Hat Enterprise Linux 3 Reporter: Jeff Moyer <jmoyer>
Component: autofsAssignee: Jeff Moyer <jmoyer>
Status: CLOSED ERRATA QA Contact: Brock Organ <borgan>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.0CC: ikent
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: RHBA-2006-0459 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-07-20 14:44:14 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 181405    

Description Jeff Moyer 2006-05-05 20:48:49 UTC
Description of problem:

It is common to have a master map which solely references a YP map, as follows:


The current included map support precludes the use of such maps, as it falsely
detects this as a recursive map inclusion.  (Well, it actually works for
auto.master, but not for any other map).

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
Setup a master map:

/misc   /etc/auto.misc

Setup auto.misc:


automount: files nis


# service autofs start

The automounter will fail to load the nis map.

If everything works properly, the automounter would create a /misc directory,
and you would see a list of directories from the yp map auto.misc.  (to obtain
the map contents of auto.misc, simply do a 'ypcat -k auto.misc').

Comment 6 Red Hat Bugzilla 2006-07-20 14:44:14 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.