[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: fsfs rep on Win98SE lock file problem

From: Josh Pieper <jjp_at_pobox.com>
Date: 2005-04-15 22:36:59 CEST

Greg Hudson wrote:
> On Fri, 2005-04-15 at 10:14, Steve Beet wrote:
> > I've just picked up on this thread - better late than never. I have the same
> > problem with checkouts under Windows ME. I'm currently on SVN 1.1.4 and
> > Tortoise SVN 1.1.5. Both behave the same (as did 1.1.3).
> >
> > Any chance of providing a workaround or a proper fix? I'd love to dump CVS and
> > migrate to SVN but until I can get around this problem, it's not practical.
> The list has mostly decided that these platforms are a low priority.
> I'm unlikely to put in the work myself.
> However, if someone else wants to look into it, the change is fairly
> simple: there's this "recovery lock" in the repository library, which
> was designed for the specific needs of the BDB back end. It doesn't
> really make sense for FSFS, which has no recovery operation and which is
> designed to allow completely unlocked read access. So the lock was
> added at the wrong layer, but we can't do anything about that. The fix,
> then, is to make libsvn_repos not use the recovery lock when the
> repository is of type FSFS.

I was actually planning on using the repository recovery lock to
implement an "svn obliterate" like functionality. I think it could be
useful for other unforseen repository manipulating activities as
well. Is there no way to have an exclusive write, shared read lock on


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Apr 15 23:20:35 2005

This is an archived mail posted to the Subversion Dev mailing list.