We've migrated one of our CVS repos to SVN, and so far so good (mostly).
A few kind of related questions...
1) The repo has barfed a few times and we needed to run svnadmin recover
to get the db into a consistent state. Assuming we're not monkeying
around with the files directly, any ideas as to a likely cause of this?
Are there any operations where you need to explicitly lock the
repository before beginning? I know this is kind of a vague question; so
far, I haven't been able to isolate a specific cause.
We are using Trac a good bit to view the source tree if it matters.
2) Assuming the db files are to be owned by the Apache user, do I need
to run svadmin as user apache (via sudo) to ensure consistent
permissions? If I run svnadmin as root, the ownership of the files gets
changed.
3) If I want to allow a group of users to run svnadmin without using
sudo, can I set group-write on the db and chgrp to an svn-admin group?
This is how I set things up originally, but the permissions keep getting
reset.
I have it setup like so:
drwxrwsr-x 2 apache svn-admin 4096 Nov 14 13:36 ./
drwxrwsr-x 7 apache svn-admin 4096 Nov 3 17:00 ../
-rw-rw---- 1 apache svn-admin 2206 Nov 3 17:00 DB_CONFIG
-rw-rw---- 1 apache svn-admin 24576 Nov 14 12:45 __db.001
-rw-rw---- 1 apache svn-admin 1318912 Nov 14 12:45 __db.002
-rw-rw---- 1 apache svn-admin 393216 Nov 14 12:45 __db.003
-rw-rw---- 1 apache svn-admin 1327104 Nov 14 12:45 __db.004
-rw-rw---- 1 apache svn-admin 16384 Nov 14 12:45 __db.005
however when svnadmin recover runs, it sets things back to 0644. Is
there a way to tell svn to maintain certain permissions / ownership on
the db files?
This is all running on RHEL 5 Beta with subversion 1.3.2.
w
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Nov 14 23:28:12 2006