[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: (ITS#7581) adding meta backend in cn=config with ldapadd / ldapmodify

hyc@symas.com wrote:
> dcoutadeur@linagora.com wrote:
>> Full_Name: dcoutadeur
>> Version: 2.4.35 / git
>> OS: openSuse 11.3 x86_64
>> URL:
>> Submission from: (NULL) (80.67.162.201)
>>
>>
>> I apologize in advance if this is not considered as a bug, but I thought this
>> ticket should help the community anyway...
>>
>> The problem is that it seems impossible to add meta backend in cn=config thanks
>> to ldapadd / ldapmodify clients. I thought the major interest for cn=config was
>> precisely to let administrators change the configuration in a remote way, but
>> maybe new database configuration is an exception ?
>
> Seems we need some rework here to allow this case. Currently bconfig assumes
> that the olcDatabaseConfig entry is sufficient by itself, and any child
> entries underneath are just optional. It doesn't handle the case where the
> olcDatabaseConfig entry is basically an incomplete config.

Should work now in git master, please test.

-- 
   -- Howard Chu
   CTO, Symas Corp.           http://www.symas.com
   Director, Highland Sun     http://highlandsun.com/hyc/
   Chief Architect, OpenLDAP  http://www.openldap.org/project/