Red Hat Bugzilla – Bug 172694
Defines not getting expanded
Last modified: 2007-11-30 17:07:21 EST
Same thing happens with autofs-4.1.3-155 on RHEL4
+++ This bug was initially created as a clone of Bug #172692 +++
When using defines in the auto.master, the variables that require shell
expansion aren't getting substituted.
For example, in auto.master:
/mnt/testnfs /etc/auto.testnfs -D OSREL=RHEL-4 -D OSUPDATE=U2 -D OSVER=AS -D
And in auto.testnfs:
You will get errors such as:
Nov 7 09:03:22 localhost automount: >> mount:
tree failed, reason given by server: Permission denied
The patch below evaluates the additional options so that shell commands can be
expanded as necessary
-- Additional comment from email@example.com on 2005-11-08 09:46 EST --
Created an attachment (id=120813)
Shell expansion is not supported in autofs configuration files. If you want
shell expansion, try using a program map.
This functionality is neither documented nor supported. I understand the
"preserve functionality, bug for bug," mentality, but the ability to do this is
going away in the next release of our operating system, anyway.
The following variables are defined by default:
ARCH The application architecture is derived from the output of uname -m
CPU The output of uname -p
Why can't the customer use one of these?
Customer's original auto.* files are attached to the IT#, but basically they
have different versions of their custom application for particular arch and base
kernel version, so they are doing a claculation like:
-D OSREL=`uname -r | sed s/-[0-9.]*/-/
Which will return '2.4.21' on any RHEL-3 kernel. So basically they need more
flexibility than just ARCH and CPU.
Customer was reporting this against RHEL-3, but copying comment to this RHEL-4
ticket for the sake of completness as the regression occurs here too.
Why was this changed to MODIFIED? I'm moving it back to ASSIGNED, with a note
that I'm still not convinced that this is something which should be "fixed."
an automounter map is a configuration file. It simply does not support shell
expansion. Yes, it happened to work in previous versions, but it will not
continue to work in the future.
Have the customer try to use program maps to generate custom variables.