[svnbook] r5830 committed - branches/1.8/zh/book/ ch06-server-configuration.xml

[wuzhouhui at users.sourceforge.net]

Revision: 5830
          http://sourceforge.net/p/svnbook/source/5830
Author:   wuzhouhui
Date:     2018-11-20 14:35:11 +0000 (Tue, 20 Nov 2018)
Log Message:
-----------
1.8/zh: translation of chapter 6 in progress

Modified Paths:
--------------
    branches/1.8/zh/book/ch06-server-configuration.xml

Modified: branches/1.8/zh/book/ch06-server-configuration.xml
===================================================================
--- branches/1.8/zh/book/ch06-server-configuration.xml	2018-11-20 14:33:25 UTC (rev 5829)
+++ branches/1.8/zh/book/ch06-server-configuration.xml	2018-11-20 14:35:11 UTC (rev 5830)
@@ -8538,6 +8538,7 @@
 </screen>
     </informalexample>
 
+      <!--
     <para>Another common problem is often encountered on Unix-like
       systems.  If your repository is backed by Berkeley DB, for
       example, it occasionally creates new log files to journal its
@@ -8549,6 +8550,13 @@
       repository's <filename>db</filename> directory.  This causes all
       newly created log files to have the same group owner as the
       parent directory.</para>
+      -->
+    <para>在类 Unix 系统上还会遇到另一个常见的问题: 比如说, 如果你的仓库是使用
+      Berkeley DB 作为后端存储, 那么它很少会去创建新的日志文件来记录自己的
+      操作. 即使整个仓库都被用户组 <literal>svn</literal> 所拥有, 这些新创建
+      的日志文件也不一定属于用户组 <literal>svn</literal>, 这会导致更多的权限
+      问题. 一种比较好的解决办法是为仓库的 <filename>db</filename> 子目录设置
+      SUID, 这将使得所有新创建的日志文件都具有和父目录相同的用户组.</para>
 
     <para>Once you've jumped through these hoops, your repository
       should be accessible by all the necessary processes.  It may