The bdb backend has 'dbnosync' off by default which means that changes
should be sync'd to disk immediately. I think you may have a problem
elsewhere. Did you try to dbrecover? When dbnosync is off, what does
checkpoint do, exactly? My best guess is that it writes a checkpoint,
which may mean you don't have to dbrecover but at the same time,
everything between that checkpoint and the time the machine crashed
would be lost.
This bug isn't 'critical'. It might be normal, maybe.
Stephen
--uX2tiToO0oGq+LKk
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline
Message-ID: <email address hidden>
Date: Thu, 21 Oct 2004 08:28:09 -0400
From: Stephen Frost <email address hidden>
To: <email address hidden>
Subject: Re: slapd: checkpoint directive missed from bdb backend
--uX2tiToO0oGq+LKk Disposition: inline
Content-Type: text/plain; charset=us-ascii
Content-
Greetings,
The bdb backend has 'dbnosync' off by default which means that changes
should be sync'd to disk immediately. I think you may have a problem
elsewhere. Did you try to dbrecover? When dbnosync is off, what does
checkpoint do, exactly? My best guess is that it writes a checkpoint,
which may mean you don't have to dbrecover but at the same time,
everything between that checkpoint and the time the machine crashed
would be lost.
This bug isn't 'critical'. It might be normal, maybe.
Stephen
--uX2tiToO0oGq+LKk pgp-signature; name="signature .asc" Description: Digital signature Disposition: inline
Content-Type: application/
Content-
Content-
-----BEGIN PGP SIGNATURE-----
MPqB3kigRAg8DAK CEVTD99vEW2hMYp 0lBzk6YdvgQSwCf Ys0P +S3Jx/9s=
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFBd6tZrzg
BvJqfIumWPaVrmh
=GTgL
-----END PGP SIGNATURE-----
--uX2tiToO0oGq+ LKk--