--On Tuesday, November 18, 2008 1:37 PM -0800 Howard Chu <hyc(a)symas.com>
Rein Tollevik wrote:
> Quanah Gibson-Mount skrev:
>> --On Saturday, November 15, 2008 10:36 PM -0800 Howard Chu
>> <hyc(a)symas.com> wrote:
>>> As a side note, test053 is not in RE24. Should it be? Seems likely...
>> No, it should not. I've already removed it once from RE24:
>> 126.96.36.199 Mon May 5 21:32:15 2008 UTC; 6 months, 1 week ago by quanah
>> Branch: OPENLDAP_REL_ENG_2_4
>> Changed since 188.8.131.52: +1 -1 lines
>> Diffs to 184.108.40.206 (colored diff)
>> FILE REMOVED
>> Remove test053-syncprov-glue. It assumes options that aren't valid for
>> earlier versions of BDB, and it assumes the db_stat in the user's path
>> is from the same version of BDB as OpenLDAP was compiled against.
> I have updated the script to try if any db_stat it finds in PATH works
> with the bdb OpenLDAP was compiled with before actually making use of
> it. Does this make the script acceptable?
> Alternatively, we could remove its db_stat usage. It is only used as an
> extra aid in detecting the deadlock situation the script was written to
> find, and to warn the user about a possible deadlock if the bug appears
> to be there. Or is there some other safe way to find a working db_stat
> to use, or test the "db_stat -V" output of any if finds agains the bdb
> version OpenLDAP was built with?
On some platforms it's called "slapd_db_stat" or somesuch. There's
no guaranteed way to find the right exe.
And, for example, in my case, it's not in my path. ;)
Principal Software Engineer
Zimbra :: the leader in open source messaging and collaboration