Re: FW: FW: Berkeley DB error while opening `changes' table for filesystem [#8143]

Hey,

>If we call DB_ENV->set_errfile(), what FILE * do we pass it? Do we
>open a unique filename (perhaps with a timestamp in its name) for
>every time we open a BDB environment, and clean up the file if there
>are no errors?
>
>

A little more ammo for deleting set_berkeley_errcall from the FS API ;-)

In my Pluggable-DB document I propose deleting set_berkeley_errcall. In
its place I want to develop an FS logging feature.
set_berkeley_errcall uses set_errcall. I believe that set_errcall
should be used instead of set_errfile. It can then be integrated into
an FS logging feature. THE set_errcall callback function SHOULD NOT BE
PASSED AS PART OF THE FS API IMNHO:-)

Currently, in my document, I don't detail what I want to develop for the
logging feature. I can spend a little time to propose something here on
the list or I can put it in my Pluggable-DB document. Which do you prefer?

gat

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue May 27 15:09:46 2003