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

Hotcopy does not keep db write-lock or txn-current-lock

From: petermity <6t12-n6js_at_dea.spamcon.org>
Date: Thu, 30 Apr 2009 01:08:38 -0700

I was verifying our backup process (hotcopy all repos, tar those
up). It wasn't identical. In each repo's db directory, there is
a 0-length file named write-lock. In some repos there is also a
0-length file txn-current-lock. Are these important? A freshly
created project has both, so it seems like they might be of some
importance, but then why doesn't hotcopy keep them? This is
Subversion 1.6.1 on Linux.

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2010096

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-05-01 09:30:06 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.