Florian,
I think I understand your question, let me know if I've missed the
mark. Berkeley database environments (DB_ENV) are free threaded, there
are a set of files maintained in the DB_HOME directory that are memory
mapped into each process opening a DB_ENV. DB has no concept of users
or user IDs. So, for Subversion, if you have many different svn
processes running at once you can open the a DB_ENV in each of those
processes referencing the same DB_HOME. The locks are implemented in
shared memory, not as signals.
does that answer the question?
-greg
_____________________________________________________________________
Gregory Burd 617-869-0997
Product Manager gburd@sleepycat.com
Sleepycat Software, Inc. http://www.sleepycat.com/
On Sep 20, 2004, at 2:44 PM, Florian Weimer wrote:
> * Gregory Burd:
>
>> Also, I've opened a support request to track a database corruption
>> issue.
>
> Ah, great.
>
> There's one thing on my list which I wanted to investigate, but it
> looks more complex than I imagined: Can Berkeley DB database
> environments be shared across different user IDs? This seems to be a
> common usage case for Subversion, but I'm not sure if it's actually
> supported by BDB.
>
> For example, if the low-level mutexes that are shared between
> processes are implemented using signals, this scenario doesn't work
> because a process that releases a mutex might not have the necessary
> privileges to send a signal to another process which is waiting for
> this mutex.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Sep 21 14:41:24 2004