I am not completely sure. Part of the problem is that in order to add
sqlite3 support into RPM, I needed to emulate the abilities of
BerkleyDB. RPM has built-in assumptions as to what works and doesn't.
I am still looking into possibly modifying RPM to do the closeall,
reopen.. but I need to figure out "where".
--Mark
[EMAIL PROTECTED] wrote:
Mark Hatle <[EMAIL PROTECTED]> writes:
Does anyone have any suggestions on how to solve this? Inform sqlite of
the root portion of the path? Temporarily disable the journal when the
chroot operation will be performed? Or some other mechanism?
Are you able to just close the database file prior to the chroot() and reopen
it afterwards? If you can do that, it should solve this problem.
Derrell
