Hey,
kfogel@collab.net wrote:
>"Sander Striker" <striker@apache.org> writes:
>
>
>>[Forwarded to the dev@ list with permission]
>>
>>-----Original Message-----
>>From: Keith Bostic [mailto:bostic@abyssinian.sleepycat.com]
>>
>>Also, Berkeley DB should always be outputting additional error
>>information whenever when it returns EINVAL, do you configure
>>your systems to log those additional errors? That might give
>>us more information to to work with, as well. If you're not
>>familiar with the additional error information messages, see the
>>DB_ENV->set_errfile and DB->set_errfile method documentation.
>>
>>
>
>
>
OK so now I have guilt:-)
I was about to start a patch that provided error logging and involved
sneaking in some of my evil plans for configs.
I wanted to pass the svn_fs_t structure to the db_errcall_fcn. But, I'm
thinking it's badness to slip an opaque reference in there considering
it's a const char *. ;-) So I stopped.
However, there is a cheap and dirty way to add logging using
DB_ENV->set_errcall or DB->set_errcall instead of set_errfile.
Install a "db_errcall_fcn that:
1. Opens a unique file using some time stamp scheme and uses apr
functions to create and open the file. (We can prefix it with the errpfx).
2. Writes the message to the file.
3. Closes the file.
Pros:
1. No need to create or clean up a file.
2. Never gets involved unless additional error info is available.
3. I stop working on my ever growing document.
4. ???
Cons:
1. One file per error message.
2. May be unable to open the file at that time. (Not a huge deal).
3. ???
Would you like a patch for this?
gat
Hmmm: I could still put in some config changes to turn this feature on
and off:-)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed May 28 22:10:24 2003