From: Michael Blandford <michael@kmaclub.com>
To: Ian Kent <raven@themaw.net>
Cc: autofs mailing list <autofs@linux.kernel.org>
Subject: Re: Problem with autofs 3.1.7 -> 4.1.0-beta2
Date: Sun, 07 Dec 2003 15:15:14 -0700 [thread overview]
Message-ID: <3FD3A672.20405@kmaclub.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0312072016350.3078-100000@raven.themaw.net>
Ian Kent wrote:
>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
~
>>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.
>
>
>
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.
Michael
next prev parent reply other threads:[~2003-12-07 22:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-07 4:34 Problem with autofs 3.1.7 -> 4.1.0-beta2 Michael Blandford
2003-12-07 5:53 ` Ian Kent
2003-12-07 6:43 ` Michael Blandford
2003-12-07 12:29 ` Ian Kent
2003-12-07 22:15 ` Michael Blandford [this message]
2003-12-07 9:14 ` H. Peter Anvin
2003-12-10 10:35 ` Ian Kent
2003-12-11 4:59 ` Michael Blandford
2003-12-11 6:45 ` Ian Kent
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3FD3A672.20405@kmaclub.com \
--to=michael@kmaclub.com \
--cc=autofs@linux.kernel.org \
--cc=raven@themaw.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.