seems to, yes (some values changed, but consistently):

# ldapsearch -LLL -h oldserver.briandomain.com -x -s base -b ''
namingcontexts
dn:
namingcontexts: dc=briandomain,dc=com


However, when I go to the "oldserver" and look in the logs, I see this:

conn=1416 op=1 SRCH base="dc=brian,dc=internal" scope=0
filter="(objectClass=*)" attrs="namingContexts"


Since I'm going from "dc=briandomain,dc=com" to "dc=brian,dc=internal"
 (mostly due to the forward and reverse lookups, which I don't want to mess
around with extensively for the actual domain) then looking for
namingContexts within that base won't work; I would like instead to just
grab everything from one base, and import it in to the new base.

Is it not working as you would expect it?  Or, is it just not possible to do
what I'm wanting?

Thanks :)
Brian



On Wed, Sep 22, 2010 at 12:44 PM, Rob Crittenden <rcrit...@redhat.com>wrote:

> Brian LaMere wrote:
>
>> I know about --user-container and --group-container, but that's not
>> sufficient; the domain is different, so I want to completely change the
>> search base for migration.  Is this possible?
>>
>> Thanks!
>> Brian
>>
>
> It looks like it tries to auto-detect the remote search base using the
> equivalent of:
>
> ldapsearch -h remote_host -x -s base -b '' namingcontexts
>
> So for example, on my LDAP server it returns:
>
> dn:
> namingcontexts: dc=example,dc=com
>
> Does this do the right thing for you?
>
> rob
>
_______________________________________________
Freeipa-users mailing list
Freeipa-users@redhat.com
https://www.redhat.com/mailman/listinfo/freeipa-users

Reply via email to