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

a question about txn-current and txn-current-lock

From: Jim the Standing Bear <standingbear_at_gmail.com>
Date: Fri, 14 Aug 2009 00:30:13 -0400


I encountered an SVN issue with txn-current and txn-current-lock, and
was wondering if some of you experts could offer some clues. Here is
the situation:

We have 3 people (user1, user2, and me, of course) working on a
project, and are all members of the linux group that is named after
the project. One of us (user1) created the SVN repository and also
started the svnserve under his account as a daemon (so we didn't
create svn user and svn group).

The repository originally contained only empty folders for the project


After we refactored some 3rd-party legacy codes, I was trying to
commit everything into core only. But then I got an error saying
Can't open db/txn-current-lock file: permission denied. An ls -l of
the db directory revealed the following:

-rwxrwxr-x 1 user2 project 3 Jul 2 17:12 current
-rwxrwxr-x 1 user2 project 3 Jul 2 17:12 txn-current
-rwxrwxr-x 2 user1 project 0 Jun 19 11:20 txn-current-lock

This seems to be a common problem, and the solution is to create an
svn user group. However, when I tried to commit things separately (a
few source files at a time), everything went in fine and I didn't
encounter this permission problem. Yet the txn-current-lock is still
owned by user1 even after I made the commit.

So my questions are:

1. do we must create svn user and group and run svnserve under that
account (my guess is no, but still want to check)?

2. what is txn-current and what is txn-current-lock? For what reasons
were they created? It seems the lock was placed much earlier (Jun 19)
by user1, but user2 manged to check in something later (on Jul 2),
pretty much the same way that I committed these files

3. related to question 2, why committing a few files at a time worked,
but committing everything at once didn't? What is the difference
between the two? Is there a way to release the txn-current-lock?

Thanks in advance!

-- Jim


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-08-14 06:53:48 CEST

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.