Hi, folks,
The docs said to post bug reports here with detailed explanations.
My problem may be a doc issue, or it may be a FAQ, but I have
not found the answer looking at a mixture of man pages, web pages,
and kernel source. The problem shows up for me on a SuSE 7.0 system
on S/390 Linux. SuSE 6.4 systems (both S/390 and INTeL based)
do not manifest this problem. They work.
Looks like there is a parsing problem when the maps are consulted.
In the maps at our site, we have a mixture of mountable volumes
and mountable directories. The former have one colon in their
map entries; others have two. Those with two colons get
"permission denied" errors when using the latest Linux automounter.
The tradition has been (I think this originated with Sun)
that if the mountable object is a volume, the syntax is "host:path".
But if the object to be mounted is a sub-directory of a shared volume,
the sub-dir is coded with a colon like this ... "host:path:subdir".
For example from "auto.home":
mything -rw,hard,intr server:/export/bigvolume:mysubdir
yourthing -rw,hard,intr server:/export/smallvolume
For the above two entries, on my SuSE 7.0 host,
/home/mything fails and /home/yourthing succeeds.
On my SuSE 6.4 hosts, both work.
Both 6.4 and 7.0 report "Linux automount version 4.0.0"
from '/usr/sbin/automount -v'. How come ftp.kernel.org
only has 3.1.7 sources?
I hope this is useful info.
There was also a problem with quotes in the maps
which I never reported. (Noticed it a year or more ago.)
But it is much less of an issue for me here.
