>> I'm most certainly overdoing : the first step is to start the server, which >> is all but a good idea. I have to simply read the configuration instead, >> because this is all what I need.
You mean it doesn't have to use or start a server to run the repair process, right. If so it sounds good, because purely running a repair tool against the database would be easy to use. Later it can also be a healthy check tool. Regards, Kai -----Original Message----- From: Emmanuel Lécharny [mailto:elecha...@gmail.com] Sent: Friday, January 29, 2016 3:41 PM To: Apache Directory Developers List <dev@directory.apache.org> Subject: Re: Database corruption repair tool Le 29/01/16 07:41, Zheng, Kai a écrit : > Thanks for the great work, Emmanuel. > > I have some questions. As discussed previously, it's hard to recreate the > database corrupt issue. Did you include a test with a sample corrupt database > image and show if it's can be repaired? All the work in a unit test or > integration test. Does the repair process just read the database image > without any updating or writing? Sorry I don't get the chance to understand > the work in details, and it's possible you have done that already. If so > please ignore my concerns. Thanks. Note that atm, it works in a unit test, but when run outside, I'm facing issues. I'm most certainly overdoing : the first step is to start the server, which is all but a good idea. I have to simply read the configuration instead, because this is all what I need. I'll most certtainly will come with a lighter version this week-end.
