Geek Answers Handbook

Subversion creates version directories with too strict permissions

This morning I tried to audit Subversion and found that suddenly I did not have permission to do so.

Can't move '/svn/db/txn-protorevs/21000-ga9.rev' to '/ svn / db / revs / 21/21001':
Permission Denied

Looking at the revs directory, I noticed that someone had completed the 21,000th revision, and for some reason there was no write permission for the new directory.

    drwxrwsr-x 2 svn svn 24K 2008-10-27 10:04 19
    drwxrwsr-x 2 svn svn 24K 2008-12-18 07:13 20
    drwxr-sr-x 2 jeff svn 4.0K 2008-12-18 11:18 21

Setting permission to write groups in this directory allows me to complete, so I am ready for another 1000 revisions. But why is this happening, and what can I change to make sure that this does not happen again?

+5
source share
3 answers

If you have more than one developer accessing the repository through the protocol file://, you might want to examine the configuration of the Subversion server (using svnserveeither Apache). With this solution, the server itself is responsible for all access rights and permissions on the repository files, and you will not encounter this problem.

From the SVN Book :

  • , URL file://. , . : ( ) , , ( . " " ). , , svn+ssh:// URL- - , , , file://, , isn .
+8

- .

( , file://), svnserve :

svnserve -d -r /svn

. .

- , .

, Apache SVN, , . . .

, , reset, file://, umask (002) svn script, :

#!/bin/bash
# svnwrapper.sh
umask 002
/usr/bin/env svn $*

, umask .

+2

, . - file:// umask.

0

More articles:


All Articles