It seems that svnadmin and family take out BerkeleyDB locks to
stablise the database during their operation. As a result they can
also cause new logs to be created and other permissions issues. Patch
below adds a note to the checklist to this effect.
<<<
Add warnings about using svnadmin et al to svn+ssh checklist.
* doc/book/book/ch06.xml: add warnings about svnadmin to checklist.
>>>
Index: doc/book/book/ch06.xml
===================================================================
--- doc/book/book/ch06.xml (revision 10470)
+++ doc/book/book/ch06.xml (working copy)
@@ -2020,6 +2020,13 @@
binary.</para>
</listitem>
+ <listitem>
+ <para>The svnlook and svnadmin commands take BerkeleyDB
+ locks on the database so they can also cause permissions
+ issues. These must also be run from a user with a sane
+ umask, or the commands themselves wrapped as above.
+ </listitem>
+
<listitem>
<para>When BerkeleyDB creates new logfiles, they need to be
owned by the group as well, so make sure you run
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Aug 3 15:00:57 2004