4.6.18/19 and chroot on unix environments

Question

Hello
Looks like BDB is caching names (and paths) of it's databases somewhere (in cache files __db* probably). This started to happen with 4.6.18.
This makes a problems when opening database, doing chroot() and making some operations on db.
Is there a way to stop caching database paths in bdb 4.6 and get the same behaviour as it was in 4.5.20?
Using db from inside and outside of chroot() makes nasty problems happen like DB_PAGE_NOTFOUND etc.

Answer 1

The code I'm trying to get working is quite huge (rpm package manager) so I'll describe what I figured out for now.
So suppose that you have directory where BDB database lives (db files + __db.XX files in the same directory):
/level1/superdir/database/
We open (dbenv->open()) that database, do something on it and close() but without calling remove(). So now we have nicely closed database but __db.XX files are still there.
Now we chroot() into /level1/ and run our program again. Since we chrooted /level1/ is now our new root directory. BDB lives in /superdir/database/ now.
So we open() /superdir/database/ and... BDB tries to open still old /level1/superdir/database/ path instead of just /superdir/database/ (after chroot path).
BDB 4.5 was working without problems with such scheme. BDB 4.6 has problems with it.
What can I do about that to get 4.5 behaviour back?
Current bdb 4.6 behaviour means that location of database directory cannot be changed without requirement to rm __db.XXX files. BDB 4.5 behaviour was nicer.