On 31/08/2007, Ron Wilson <firstname.lastname@example.org> wrote:
> On 8/31/07, Stefan Küng <email@example.com> wrote:
> > Strip, David R wrote:
> > > I was not aware of the vulnerability under FILE://, but now that you
> > > mention it, I'm guessing the problem arises when two (or more) people
> > > try to commit (or otherwise modify) the repository at the same time.
> > > Since FILE:// provides no directory level locking, you can get seriously
> > > hosed. Is that the issue?
> > Whether directory level locking is available or not depends fully on the
> > network protocol and the filesystem on the server. If both support it,
> > Subversion can use it and you will be fine even if multiple accesses
> > happen at the same time. But lets face it: there simply isn't a network
> > that stable to never have problems. And one cut connection is enough to
> > leave a lock in the repository - you will have to execute an 'svnadmin
> > recover' on the repository before any other access will be possible.
> > And of course, if you run that command over the network and someone
> > tries to access the repo that very moment, your repository could get
> > screwed beyond repair. (svnadmin recover can't lock - it has to *remove*
> > left over locks, that's why an access at that time is fatal).
> Unfortunately, there are some environments where the file:/// method
> is the only option. I am working in such an environment. It is very
> hard to get the IT people to grant us a DB on the MS SQL server or
> even a MS extension to IIS, let alone get them to set up any other
> kind of server. We were able to get a server folder under which we put
> all our group's shared resources, including the SVN repositories.
> (Fortunately, they long ago gave up on trying to support the "arcane"
> needs of embedded software development and give us admin rights to our
You might see if they will let you use svnserve. It's very compact
compared with apache or IIS, and it won't interfere with IIS or MS SQL
in any way. It's also easier to run as a service, starting with 1.4.
Aside from backing up the repository, along with everything else on
the network, there is nothing they need to administer. Maybe worth a
And if they still won't listen, you can still set up svnserve on a
local machine (like yours), run as a service. As long as that machine
is switched on, you have a working server, even if you're not logged
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Sat Sep 1 00:53:45 2007