All of lore.kernel.org
 help / color / mirror / Atom feed
From: wengang wang <wen.gang.wang@oracle.com>
To: Ian Kent <raven@themaw.net>
Cc: autofs@linux.kernel.org
Subject: Re: basedn in /etc/sysconfig/autofs
Date: Mon, 10 Sep 2007 09:44:32 +0800	[thread overview]
Message-ID: <46E4A180.2000409@oracle.com> (raw)
In-Reply-To: <1189050061.3102.27.camel@raven.themaw.net>


[-- Attachment #1.1: Type: text/plain, Size: 3412 bytes --]

Hi Ian,

reply from custom:
==>
Just to clarify:
 
1. We use different basedn for authentication and automount in our 
directory. The basedn for authentoication is used from /etc/ldap.conf. 
However we need to specify a separate basedn for automount maps because 
they are regional.
 
2. We do not have multiple master maps just one.
 
If it possible to use the MASTER_MAP_NAME without specifying the server 
then that should solve our problem. I will test this and let you know if 
it works.
<==

thanks,
wengang.

Ian Kent wrote:
> On Thu, 2007-09-06 at 10:01 +0800, wengang wang wrote:
>   
>> Hi Ian,
>>
>> here is the exchangings:
>>     
>
> It's not clear from this what the problem is.
>
> snip ...
>
>   
>> *** PLAKDAWA  08/14/07 02:06 pm *** 
>> Just to give you a little more information: Our automount schema is
>> based on 
>> the "automountmapname", "automountkey" and "automountinformation"
>> attributes. 
>> This works properly with the relevant settings in
>> the /etc/sysconfig/autofs 
>> file on RHEL5 if the basedn is set manually in
>> the /etc/openldap/ldap.conf 
>>     
>
> But doesn't work if you don't set basdn in ldap.conf?
> Are you saying that there are multiple master maps and maps of the same
> name under different basedns in this setup?
>
>   
>> file. However, since the openldap/ldap.conf file can be used by other 
>> applications, we don't want our automounter's basedn to depend on
>> this. 
>>
>> The LDAP attributes of the automount maps are as shown below: 
>>
>> [porus@rattlebag ~]$ ldapsearch -LLL -x -b 
>> "ou=sc,ou=ca,ou=na,dc=hyperion,dc=com"
>> "automountmapname=auto_nfshome" 
>> dn:
>> automountMapName=auto_nfshome,ou=sc,ou=ca,ou=na,dc=hyperion,dc=com 
>> objectClass: top 
>> objectClass: automountMap 
>> automountMapName: auto_nfshome 
>>   
>> [porus@rattlebag ~]$ ldapsearch -LLL -x -b 
>> "automountmapname=auto_nfshome,ou=sc,ou=ca,ou=na,dc=hyperion,dc=com" 
>> "automountkey=plakdawa" 
>> dn: 
>> automountkey=plakdawa,automountMapName=auto_nfshome,ou=sc,ou=ca,ou=na,dc=h 
>>  yperion,dc=com 
>> automountInformation: scfs3:/vol/vol2/homes/& 
>> automountKey: plakdawa 
>> objectClass: top 
>> objectClass: automount 
>>     
>
> snip ...
>
>   
>> *** PLAKDAWA  08/20/07 11:51 am *** 
>> The other issue with the DEFAULT_MASTER_MAP_NAME is that providing the full 
>> URL, will prevent the failover to the secondary LDAP server should the one 
>> mentioned in the URL fail. Or is it possible to add secondary entries?
>>     
>
> It's possible to specify the map (master or other) without the server
> name.
>
> eg.
> MASTER_MAP_NAME="ou=auto.master,dc=themaw,dc=net"
>
> This will then use the above basedn for finding the master map.
>
> However, this can't be used when autofs searches for the basedn for the
> maps referred to in the above master map which may not be a sensible
> thing to do but cannot be practically done another way. 
>
> The only workaround for this at the moment would be to specify the
> basedn in the master map entries as well as in the master map as above.
>
> eg.
> # /ldap, auto.master, themaw.net
> dn: cn=/ldap,ou=auto.master,dc=themaw,dc=net
> objectClass: automount
> cn: /ldap
> automountInformation: ou=auto.indirect,dc=themaw,dc=net
>
> Ian
>
>
>   

-- 
Wengang Wang
Member of Technical Staff
Oracle Asia R&D Center
Open Source Technologies Development

Tel:      +86 10 8278 6265
Mobile:   +86 13381078925


[-- Attachment #1.2: Type: text/html, Size: 4892 bytes --]

[-- Attachment #2: Type: text/plain, Size: 140 bytes --]

_______________________________________________
autofs mailing list
autofs@linux.kernel.org
http://linux.kernel.org/mailman/listinfo/autofs

  reply	other threads:[~2007-09-10  1:44 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-05  2:15 basedn in /etc/sysconfig/autofs wengang wang
2007-09-05 12:16 ` Ian Kent
2007-09-05 17:43   ` Simon Gao
2007-09-05 17:57     ` Wolfe, Allan
2007-09-06  3:11       ` Ian Kent
2007-09-06  3:09     ` Ian Kent
2007-09-06 14:43       ` Jeff Moyer
2007-09-06 22:44         ` Simon Gao
2007-09-07  1:14           ` Ian Kent
2007-09-06  2:01   ` wengang wang
2007-09-06  3:41     ` Ian Kent
2007-09-10  1:44       ` wengang wang [this message]
2007-09-10  3:01         ` 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=46E4A180.2000409@oracle.com \
    --to=wen.gang.wang@oracle.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.