Re: Getting exclusive access to the repository

On Thu, Jan 23, 2003 at 07:01:30PM -0500, Eric Gillespie wrote:
 Philip Martin philip@codematters.co.uk writes:
...
  It would be better if one could a) lock the database and
  prevent new conections, then b) wait for the administrator to
  verify that there are no existing connections, and finally c)
  run recover.
 
 What's the point? This is already easily done.

If you're trying to keep your Apache web server up and running and servicing
other needs, then stopping it sucks majorly.

The whole point of REPOS/lock/db.lock is to arbitrate access. svnadmin is
supposed to take out a write lock on that file, thus blocking any new
entrants until svnadmin is done.

Of course, the problem is what to do with people already hung up in the
database awaiting some DB lock that won't come back? Basically, you start up
svnadmin, it blocks on the DB lock, then you kill the other processes and
they release REPOS/lock/db.lock, then the svnadmin proceeds.

Is that what we implemented? Nah. svnadmin attempts to unlock db.lock for
some reason...

Cheers,
-g

-- 
Greg Stein, http://www.lyra.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org