Red Hat Bugzilla – Bug 143074
autofs variables not passed on to submounts
Last modified: 2007-11-30 17:07:05 EST
if /sbcimp is handled by the automounter, and a submount is defined
for /sbcimp/dyn/logfiles, variables passed to the automounter for
/sbcimp won't be passed for the submount.
Created attachment 108685 [details]
Patch from Ian McLeod <firstname.lastname@example.org> (in case it wasn't clear from the
> Patch from Ian McLeod <email@example.com> (in case it wasn't clear
> from the patch ;)
Heh. I guess it is a bit over-annotated. Any thoughts on when this
might be incorporated into an updated autofs package?
It's on track for RHEL3 Update 5.
Created attachment 111552 [details]
This patch should address the propagation of variables to submounts.
This is the patch from upstream. I have tested it in my environment and it
A package containing this fix was committed to the RHEL 3 pool. The
package version is 4.1.3-104. Please test this during the beta window.
We're investigating this.
The logs indicate that autofs is using the YP maps, but it appears that the maps
included in the bug report are the file maps from /etc/.
Could you please include the output from:
ypcat -k auto.local
ypcat -k auto.sub1
ypcat -k auto.sub2
Created attachment 113574 [details]
Strip spaces from the end of the 'loc' string.
We've reproduced the problem in-house, and have come up with this patch to fix
it. Spaces were not being stripped from the map name, causing this problem.
With the attached patch, everything is working as expected.
You can find RPMS with the patch applied at:
Please retest and update this bug with your results.
Jeff, I've just tested with this -124 version of autofs and the submount maps
are working as expected now & the map variables are getting correctly passed to
the submount daemons. So this version looks good to resolve this bug.
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.