Re: (ITS#5755) Schema file not always converted to LDIF and slapdwon't restart

[hyc@symas.com]

emmanuel.duru@atosorigin.com wrote:
> OK this works.
> My mistake, the concerned character is in fact a Windows character (CP1252)
> I hadn't noticed when I converted my schema to a text file.

With the patch in HEAD your schema file now yields:

config_build_attrs: error 21 on olcAttributeTypes value #3
config_build_entry: build "cn={0}test" failed: ""
backend_startup_one: bi_db_open failed! (-1)
slapd stopped.

Probably we should be detecting this problem earlier, when parsing slapd.conf, 
instead of when generating the cn=config entries.

>> -----Message d'origine-----
>> De : Hallvard Breien Furuseth [mailto:h.b.furuseth@usit.uio.no]
>> Envoyé : lundi 20 octobre 2008 19:39
>> À : Emmanuel Duru
>> Cc : openldap-its@OpenLDAP.org
>> Objet : RE: (ITS#5755) Schema file not always converted to LDIF and
>> slapdwon't restart
>>
>> The problem is the 8-bit Latin-1 character in the certificate's DESC.
>> It works if you convert the schema file to UTF-8.
>>
>> Slapd should have refused to start with a non-UTF-8 attribute DESC.
>> Possibly that should wait for OpenLDAP 2.5 though, and just log a
>> warning for now.
>>
>> --
>> Hallvard
>
>
>
>


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