You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by petermity <6t...@dea.spamcon.org> on 2009/04/30 08:08:38 UTC
Hotcopy does not keep db write-lock or txn-current-lock
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@subversion.tigris.org].