Re: [openldap 2.1.12 + BerkeleyDb 4.1.24] db_checkpoint pb

[Helene.Lastennet@alcatel.fr]

> Hi,
>
> Does this problem occurs if you use the checkpoint
> directive in slapd.conf instead?

I don't know ...
I chose to use db_checkpoint of BerkeleyDB instead of checkpoint in
slapd.conf
because when you read the openldap doc (+ FAQ) it seems to be better to
make tuning directly in the bdb-backend rather than to use the file of
configuration slapd.conf ...?
So what can I do to be sure ?

> --- Helene.Lastennet@alcatel.fr wrote:
> > Hy,
> >
> > I have some pb with the checkpointing procedure.
> > In my crontab I added a shell script (cf. file in
> > attachment) enabling
> > to make every hour:
> > 1. db_archive (in order to remove the inactive
> > database log files)
> > 2. db_checkpoint (to write into the backing database
> > file the changes to
> > the database that are part of committed
> > transactions)
> > 3. db_archive (in order to remove again the inactive
> > database log files)
> >
> > But, often my script can be blocked (db_checkpoint
> > seems failed) and I
> > can't restart correctly openldap
> > To restart correctly my openldap server I need to
> > make a db_recover
> > But our customer is absolutely not glad to stop the
> > service regularly
> > ...
> >
> > So do you have an idea about this pb ?
> > Best regards,
> > Helene
> >
> > Working Environment :
> > Linux redhat 7.3
> > Berkley 4.1.24
> > openldap 2.1.12
> > database-backend: bdb
> >
>
> > ATTACHMENT part 2 application/x-sh
> name=dbCheckpoint.sh
>
> __________________________________
> Do you Yahoo!?
> Protect your identity with Yahoo! Mail AddressGuard
> http://antispam.yahoo.com/whatsnewfree