httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sl...@apache.org
Subject cvs commit: httpd-2.0/docs/manual/mod mod_dav.html.en mod_dav.xml mod_dav_fs.html.en mod_dav_fs.xml
Date Mon, 21 Apr 2003 20:36:40 GMT
slive       2003/04/21 13:36:40

  Modified:    docs/manual/mod mod_dav.html.en mod_dav.xml
                        mod_dav_fs.html.en mod_dav_fs.xml
  Log:
  Be a little more consistent with the pathnames, and move some
  DavLockDB details to its directive docs.
  
  Revision  Changes    Path
  1.16      +4 -8      httpd-2.0/docs/manual/mod/mod_dav.html.en
  
  Index: mod_dav.html.en
  ===================================================================
  RCS file: /home/cvs/httpd-2.0/docs/manual/mod/mod_dav.html.en,v
  retrieving revision 1.15
  retrieving revision 1.16
  diff -u -d -b -u -r1.15 -r1.16
  --- mod_dav.html.en	21 Apr 2003 14:57:50 -0000	1.15
  +++ mod_dav.html.en	21 Apr 2003 20:36:39 -0000	1.16
  @@ -65,7 +65,8 @@
       
       <p>In addition, a location for the DAV lock database must be
       specified in the global section of your <code>httpd.conf</code>
  -    file:</p>
  +    file using the <code class="directive"><a href="../mod/mod_dav_fs.html#davlockdb">DavLockDB</a></code>
  +    directive:</p>
   
       <div class="example"><p><code>
         DavLockDB /usr/local/apache2/var/DavLock
  @@ -74,12 +75,7 @@
       <p>The directory containing the lock database file must be
       writable by the <code class="directive"><a href="../mod/mpm_common.html#user">User</a></code>
       and <code class="directive"><a href="../mod/mpm_common.html#group">Group</a></code>
under which
  -    Apache is running.  For security reasons, you should create a
  -    directory for this purpose rather than changing the permissions on
  -    an existing directory.  In the above example, Apache will create
  -    files in the <code>/usr/local/apache2/var/</code> directory
  -    with the base filename <code>DavLock</code> and extension name
  -    chosen by the server.</p>
  +    Apache is running.</p>
   
       <p>You may wish to add a <code class="directive"><a href="../mod/core.html#limit">&lt;Limit&gt;</a></code>
clause inside the <code class="directive"><a href="../mod/core.html#location">&lt;Location&gt;</a></code>
directive to limit access to
       DAV-enabled locations. If you want to set the maximum amount of
  @@ -89,7 +85,7 @@
       requests.</p>
   
       <div class="example"><h3>Full Example</h3><p><code>
  -      DavLockDB /tmp/DavLock<br />
  +      DavLockDB /usr/local/apache2/var/DavLock<br />
         <br />
          &lt;Location /foo&gt;<br />
          <span class="indent">
  
  
  
  1.8       +4 -8      httpd-2.0/docs/manual/mod/mod_dav.xml
  
  Index: mod_dav.xml
  ===================================================================
  RCS file: /home/cvs/httpd-2.0/docs/manual/mod/mod_dav.xml,v
  retrieving revision 1.7
  retrieving revision 1.8
  diff -u -d -b -u -r1.7 -r1.8
  --- mod_dav.xml	21 Apr 2003 03:00:40 -0000	1.7
  +++ mod_dav.xml	21 Apr 2003 20:36:39 -0000	1.8
  @@ -35,7 +35,8 @@
       
       <p>In addition, a location for the DAV lock database must be
       specified in the global section of your <code>httpd.conf</code>
  -    file:</p>
  +    file using the <directive module="mod_dav_fs">DavLockDB</directive>
  +    directive:</p>
   
       <example>
         DavLockDB /usr/local/apache2/var/DavLock
  @@ -44,12 +45,7 @@
       <p>The directory containing the lock database file must be
       writable by the <directive module="mpm_common">User</directive>
       and <directive module="mpm_common" >Group</directive> under which
  -    Apache is running.  For security reasons, you should create a
  -    directory for this purpose rather than changing the permissions on
  -    an existing directory.  In the above example, Apache will create
  -    files in the <code>/usr/local/apache2/var/</code> directory
  -    with the base filename <code>DavLock</code> and extension name
  -    chosen by the server.</p>
  +    Apache is running.</p>
   
       <p>You may wish to add a <directive module="core" type="section"
       >Limit</directive> clause inside the <directive module="core"
  @@ -62,7 +58,7 @@
       requests.</p>
   
       <example><title>Full Example</title>
  -      DavLockDB /tmp/DavLock<br />
  +      DavLockDB /usr/local/apache2/var/DavLock<br />
         <br />
          &lt;Location /foo&gt;<br />
          <indent>
  
  
  
  1.4       +11 -1     httpd-2.0/docs/manual/mod/mod_dav_fs.html.en
  
  Index: mod_dav_fs.html.en
  ===================================================================
  RCS file: /home/cvs/httpd-2.0/docs/manual/mod/mod_dav_fs.html.en,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -d -b -u -r1.3 -r1.4
  --- mod_dav_fs.html.en	11 Dec 2002 21:11:15 -0000	1.3
  +++ mod_dav_fs.html.en	21 Apr 2003 20:36:39 -0000	1.4
  @@ -67,8 +67,18 @@
       
   
       <div class="example"><h3>Example</h3><p><code>
  -      DavLockDB logs/DavLock
  +      DavLockDB var/DavLock
       </code></p></div>
  +
  +    <p>The directory containing the lock database file must be
  +    writable by the <code class="directive"><a href="../mod/mpm_common.html#user">User</a></code>
  +    and <code class="directive"><a href="../mod/mpm_common.html#group">Group</a></code>
under which
  +    Apache is running.  For security reasons, you should create a
  +    directory for this purpose rather than changing the permissions on
  +    an existing directory.  In the above example, Apache will create
  +    files in the <code>var/</code> directory under the <code class="directive"><a
href="../mod/core.html#serverroot">ServerRoot</a></code> with the base filename
  +    <code>DavLock</code> and extension name chosen by the server.</p>
  +
   
   </div>
   </div>
  
  
  
  1.3       +12 -1     httpd-2.0/docs/manual/mod/mod_dav_fs.xml
  
  Index: mod_dav_fs.xml
  ===================================================================
  RCS file: /home/cvs/httpd-2.0/docs/manual/mod/mod_dav_fs.xml,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -d -b -u -r1.2 -r1.3
  --- mod_dav_fs.xml	11 Apr 2003 01:25:52 -0000	1.2
  +++ mod_dav_fs.xml	21 Apr 2003 20:36:39 -0000	1.3
  @@ -48,8 +48,19 @@
       the server to display all locks in a lock database.</p> -->
   
       <example><title>Example</title>
  -      DavLockDB logs/DavLock
  +      DavLockDB var/DavLock
       </example>
  +
  +    <p>The directory containing the lock database file must be
  +    writable by the <directive module="mpm_common">User</directive>
  +    and <directive module="mpm_common" >Group</directive> under which
  +    Apache is running.  For security reasons, you should create a
  +    directory for this purpose rather than changing the permissions on
  +    an existing directory.  In the above example, Apache will create
  +    files in the <code>var/</code> directory under the <directive
  +    module="core">ServerRoot</directive> with the base filename
  +    <code>DavLock</code> and extension name chosen by the server.</p>
  +
   </usage>
   </directivesynopsis>
   
  
  
  

Mime
View raw message