Which schema are you using the nisMap or automountMap.automountMap
I'll need an ldif example in order to duplicate the problem.Names are changed to protect the innocent.
# auto.master, kmaclub, com dn: ou=auto.master,dc=kmaclub,dc=com objectClass: top objectClass: automountMap ou: auto.master
# /services, auto.master, kmaclub, com dn: cn=/services, ou=auto.master,dc=kmaclub,dc=com objectClass: automount automountInformation: ldap:ou=auto.services,dc=kmaclub,dc=com cn: /services
# auto.services, kmaclub, com dn: ou=auto.services,dc=kmaclub,dc=com objectClass: top objectClass: automountMap ou: auto.services
# /, auto.services, kmaclub, com dn: cn=/,ou=auto.services,dc=kmaclub,dc=com objectClass: automount automountInformation: fileserver:/export/services/& cn: /
# mounta, auto.services, kmaclub, com dn: cn=mounta,ou=auto.services,dc=kmaclub,dc=com objectClass: automount cn: mounta automountInformation: fileserver:/export2/mounta
# mountb, auto.services, kmaclub, com dn: cn=mountb,ou=auto.services,dc=kmaclub,dc=com objectClass: automount cn: mountb automountInformation: fileserver:/export2/mountb
# mountc, auto.services, kmaclub, com dn: cn=mountc,ou=auto.services,dc=kmaclub,dc=com objectClass: automount cn: mountc automountInformation: fileserver:/export2/mountc
# mountd, auto.services, kmaclub, com dn: cn=mountd,ou=auto.services,dc=kmaclub,dc=com objectClass: automount cn: mountd automountInformation: fileserver:/export2/mountd ~
I reloaded autofs-4.1.0-beta2 again today just to play. What I have found is cd'ing into /services/asdlfjadalsdjfaklsdjf will also suceed and give me a mount to fileserver:/export2/mountb even though the mount should fail.According to the automount man page, the wildcard for ldap is a / so that is what I was using. What I thought was odd was it was always choosing the same thing and it *wasn't* the wildcard.
Think the code is incorrect.
Michael
_______________________________________________ autofs mailing list [EMAIL PROTECTED] http://linux.kernel.org/mailman/listinfo/autofs
