Re: two problems when migrating from 2.1.30 to 2.2.15

[vadim <vadim.tarassov@swissonline.ch>]

Hallo Kurt,

I have not got your point when you write

See the Berkeley DB documentation for actions required of
> you after making certain kinds of changes to DB_CONFIG.

What are "certain kind of changes"? I was always making 
ldapadd with 2.1.30 and log files were deleted. Now I 
started with empty db and 2.2.15, log files are not deleted. 
Which part of the documentation you mentioned and what are 
these changes ?!?

Now about "garbage". I know that "---" is garbage. However 
I really don't like going any further RFC when deciding how to 
process data, I believe "matter of taste" is out of scope in this discussion.

Though have not understood you message thank you anyway.

Regards, vadim tarassov.

On Sun, 2004-09-05 at 22:25, Kurt D. Zeilenga wrote:
> At 02:26 PM 9/5/2004, vadim wrote:
> >Hallo everybody,
> >
> >I am trying to move from 2.1.30 to 2.2.15. I've met two problems, which
> >I can not identify as mine at the moment, and I want to know what do you
> >think about it ...
> >
> >1) 2.2.15 does not accept value "---" of attribute telephoneNumber,
> >saying that "normalization failed". I understand that such value of the
> >attribute is just meaningless, however it is valid per syntax if I am
> >not too wrong. Who is wrong, me or ldap server?
> 
> "---" is not a telephone number.  It is proper for a LDAP server
> to disallow the addition of such garbage.
> 
> >2) I had string "set_flags DB_LOG_AUTOREMOVE" in my DB_CONFIG file. This
> >was making berkeley db to remove all unused log files after next
> >checkpoint. With 2.2.15 this parameter in DB_CONFIG does not make any
> >effect, log files remain on file system. Do you know if something has
> >changed?
> 
> See the Berkeley DB documentation for actions required of
> you after making certain kinds of changes to DB_CONFIG.
> 
> Kurt
>