Given the attached auto.master, startup fails with:
lookup(ldap): query failed for (&(objectcalss=nisObject))
lookup(ldap): query failed for (&(objectclass=automount))
failed to load map, exiting
failed to remove dir ^PP: No such file or directory.
The failed to remove directory error looks pretty bogus too.
Created attachment 98578 [details]
autofs config file
The ldap path initialization code changed between versions 3 and 4. I
ported forward the version 3 way of parsing the ldap server name and
base DN. This fix will appear in fc2t2.
Now, with a wildcard map, if I try to mount
/home/<some-user-whose-homedir-isn't-in-autofs>, it mounts the last
one in the entry.
Bill, could you provide a little more information? When you say you
try to mount, do you issue the mount command by hand? Do you try to
cd to a directory that doesn't exist? And when you say it mounts the
last one in the entry, what precisely do you mean? Exact steps to
reproduce the problem would be helpful.
I'm seeing exactly the same symptoms as Bill, using a NIS autofs map.
"ls /home/foo" where foo is caught by the wildcard results in a
directory-not-found, and the logs show autofs was trying to mount the
last entry listed in "ypcat auto.home" (which happens to be
unreachable at present, hence the mount fails.)
Appears fixed in autofs-4.1.1-1, at least for my NIS case.
autofs-4.1.1 fixed the wildcard issues. It broke ldap, though. I
fixed a bug dealing with too short timeouts, and all seems well. I've
tested the nis case and the ldap case. Both work for me in
autofs-4.1.1-3, which I built into fc2-HEAD.
Works for me.