[xiph-commits] r6947 - in websites: . conf db hooks locks
atamido at dactyl.lonelymoon.com
atamido
Fri Jul 2 08:31:12 PDT 2004
Author: atamido
Date: Fri Jul 2 08:31:12 2004
New Revision: 6947
Added:
websites/README.txt
websites/conf/
websites/conf/svnserve.conf
websites/dav/
websites/db/
websites/db/DB_CONFIG
websites/db/__db.001
websites/db/__db.002
websites/db/__db.003
websites/db/__db.004
websites/db/__db.005
websites/db/changes
websites/db/copies
websites/db/log.0000000001
websites/db/nodes
websites/db/representations
websites/db/revisions
websites/db/strings
websites/db/transactions
websites/db/uuids
websites/format
websites/hooks/
websites/hooks/post-commit.tmpl
websites/hooks/post-revprop-change.tmpl
websites/hooks/pre-commit.tmpl
websites/hooks/pre-revprop-change.tmpl
websites/hooks/start-commit.tmpl
websites/locks/
websites/locks/db-logs.lock
websites/locks/db.lock
Log:
Initial Import
Added: websites/README.txt
===================================================================
--- websites/README.txt 2004-07-02 15:18:18 UTC (rev 6946)
+++ websites/README.txt 2004-07-02 15:31:11 UTC (rev 6947)
@@ -0,0 +1,9 @@
+This is a Subversion repository; use the 'svnadmin' tool to examine
+it. Do not add, delete, or modify files here unless you know how
+to avoid corrupting the repository.
+
+The directory "db" contains a Berkeley DB environment.
+You may need to tweak the values in "db/DB_CONFIG" to match the
+requirements of your site.
+
+Visit http://subversion.tigris.org/ for more information.
Added: websites/conf/svnserve.conf
===================================================================
--- websites/conf/svnserve.conf 2004-07-02 15:18:18 UTC (rev 6946)
+++ websites/conf/svnserve.conf 2004-07-02 15:31:11 UTC (rev 6947)
@@ -0,0 +1,25 @@
+### This file controls the configuration of the svnserve daemon, if you
+### use it to allow access to this repository. (If you only allow
+### access through http: and/or file: URLs, then this file is
+### irrelevant.)
+
+### Visit http://subversion.tigris.org/ for more information.
+
+# [general]
+### These options control access to the repository for unauthenticated
+### and authenticated users. Valid values are "write", "read",
+### and "none". The sample settings below are the defaults.
+# anon-access = read
+# auth-access = write
+### This option controls the location of the password database. This
+### path may be relative to the conf directory. There is no default.
+### The format of the password database is:
+### [users]
+### USERNAME = PASSWORD
+# password-db = passwd
+### This option specifies the authentication realm of the repository.
+### If two repositories have the same authentication realm, they should
+### have the same password database, and vice versa. The default realm
+### is the path to the repository, relative to the server's repository
+### root.
+# realm = My First Repository
Added: websites/db/DB_CONFIG
===================================================================
--- websites/db/DB_CONFIG 2004-07-02 15:18:18 UTC (rev 6946)
+++ websites/db/DB_CONFIG 2004-07-02 15:31:11 UTC (rev 6947)
@@ -0,0 +1,53 @@
+# This is the configuration file for the Berkeley DB environment
+# used by your Subversion repository.
+# You must run 'svnadmin recover' whenever you modify this file,
+# for your changes to take effect.
+
+### Lock subsystem
+#
+# Make sure you read the documentation at:
+#
+# http://www.sleepycat.com/docs/ref/lock/max.html
+#
+# before tweaking these values.
+set_lk_max_locks 2000
+set_lk_max_lockers 2000
+set_lk_max_objects 2000
+
+### Log file subsystem
+#
+# Make sure you read the documentation at:
+#
+# http://www.sleepycat.com/docs/api_c/env_set_lg_bsize.html
+# http://www.sleepycat.com/docs/api_c/env_set_lg_max.html
+# http://www.sleepycat.com/docs/ref/log/limits.html
+#
+# Increase the size of the in-memory log buffer from the default
+# of 32 Kbytes to 256 Kbytes. Decrease the log file size from
+# 10 Mbytes to 1 Mbyte. This will help reduce the amount of disk
+# space required for hot backups. The size of the log file must be
+# at least four times the size of the in-memory log buffer.
+#
+# Note: Decreasing the in-memory buffer size below 256 Kbytes
+# will hurt commit performance. For details, see this post from
+# Daniel Berlin <dan at dberlin.org>:
+#
+# http://subversion.tigris.org/servlets/ReadMsg?list=dev&msgId=161960
+set_lg_bsize 262144
+set_lg_max 1048576
+#
+# Disable fsync of log files on transaction commit. Read the
+# documentation about DB_TXN_NOSYNC at:
+#
+# http://www.sleepycat.com/docs/api_c/env_set_flags.html
+#
+# [requires Berkeley DB 4.0]
+# set_flags DB_TXN_NOSYNC
+#
+# Enable automatic removal of unused transaction log files.
+# Read the documentation about DB_LOG_AUTOREMOVE at:
+#
+# http://www.sleepycat.com/docs/api_c/env_set_flags.html
+#
+# [requires Berkeley DB 4.2]
+set_flags DB_LOG_AUTOREMOVE
Added: websites/db/__db.001
===================================================================
(Binary files differ)
Property changes on: websites/db/__db.001
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: websites/db/__db.002
===================================================================
(Binary files differ)
Property changes on: websites/db/__db.002
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: websites/db/__db.003
===================================================================
(Binary files differ)
Property changes on: websites/db/__db.003
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: websites/db/__db.004
===================================================================
(Binary files differ)
Property changes on: websites/db/__db.004
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: websites/db/__db.005
===================================================================
(Binary files differ)
Property changes on: websites/db/__db.005
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: websites/db/changes
===================================================================
(Binary files differ)
Property changes on: websites/db/changes
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: websites/db/copies
===================================================================
(Binary files differ)
Property changes on: websites/db/copies
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: websites/db/log.0000000001
===================================================================
(Binary files differ)
Property changes on: websites/db/log.0000000001
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: websites/db/nodes
===================================================================
(Binary files differ)
Property changes on: websites/db/nodes
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: websites/db/representations
===================================================================
(Binary files differ)
Property changes on: websites/db/representations
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: websites/db/revisions
===================================================================
(Binary files differ)
Property changes on: websites/db/revisions
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: websites/db/strings
===================================================================
(Binary files differ)
Property changes on: websites/db/strings
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: websites/db/transactions
===================================================================
(Binary files differ)
Property changes on: websites/db/transactions
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: websites/db/uuids
===================================================================
(Binary files differ)
Property changes on: websites/db/uuids
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: websites/format
===================================================================
--- websites/format 2004-07-02 15:18:18 UTC (rev 6946)
+++ websites/format 2004-07-02 15:31:11 UTC (rev 6947)
@@ -0,0 +1 @@
+3
Added: websites/hooks/post-commit.tmpl
===================================================================
--- websites/hooks/post-commit.tmpl 2004-07-02 15:18:18 UTC (rev 6946)
+++ websites/hooks/post-commit.tmpl 2004-07-02 15:31:11 UTC (rev 6947)
@@ -0,0 +1,39 @@
+#!/bin/sh
+
+# POST-COMMIT HOOK
+#
+# The post-commit hook is invoked after a commit. Subversion runs
+# this hook by invoking a program (script, executable, binary, etc.)
+# named 'post-commit' (for which this file is a template) with the
+# following ordered arguments:
+#
+# [1] REPOS-PATH (the path to this repository)
+# [2] REV (the number of the revision just committed)
+#
+# The default working directory for the invocation is undefined, so
+# the program should set one explicitly if it cares.
+#
+# Because the commit has already completed and cannot be undone,
+# the exit code of the hook program is ignored. The hook program
+# can use the 'svnlook' utility to help it examine the
+# newly-committed tree.
+#
+# On a Unix system, the normal procedure is to have 'post-commit'
+# invoke other programs to do the real work, though it may do the
+# work itself too.
+#
+# Note that 'post-commit' must be executable by the user(s) who will
+# invoke it (typically the user httpd runs as), and that user must
+# have filesystem-level permission to access the repository.
+#
+# On a Windows system, you should name the hook program
+# 'post-commit.bat' or 'post-commit.exe',
+# but the basic idea is the same.
+#
+# Here is an example hook script, for a Unix /bin/sh interpreter:
+
+REPOS="$1"
+REV="$2"
+
+commit-email.pl "$REPOS" "$REV" commit-watchers at example.org
+log-commit.py --repository "$REPOS" --revision "$REV"
Added: websites/hooks/post-revprop-change.tmpl
===================================================================
--- websites/hooks/post-revprop-change.tmpl 2004-07-02 15:18:18 UTC (rev 6946)
+++ websites/hooks/post-revprop-change.tmpl 2004-07-02 15:31:11 UTC (rev 6947)
@@ -0,0 +1,40 @@
+#!/bin/sh
+
+# POST-REVPROP-CHANGE HOOK
+#
+# The post-revprop-change hook is invoked after a revision property
+# has been changed. Subversion runs this hook by invoking a program
+# (script, executable, binary, etc.) named 'post-revprop-change'
+# (for which this file is a template), with the following ordered
+# arguments:
+#
+# [1] REPOS-PATH (the path to this repository)
+# [2] REV (the revision that was tweaked)
+# [3] USER (the username of the person tweaking the property)
+# [4] PROPNAME (the property that was changed)
+#
+# Because the propchange has already completed and cannot be undone,
+# the exit code of the hook program is ignored. The hook program
+# can use the 'svnlook' utility to help it examine the
+# new property value.
+#
+# On a Unix system, the normal procedure is to have 'post-revprop-change'
+# invoke other programs to do the real work, though it may do the
+# work itself too.
+#
+# Note that 'post-revprop-change' must be executable by the user(s) who will
+# invoke it (typically the user httpd runs as), and that user must
+# have filesystem-level permission to access the repository.
+#
+# On a Windows system, you should name the hook program
+# 'post-revprop-change.bat' or 'post-revprop-change.exe',
+# but the basic idea is the same.
+#
+# Here is an example hook script, for a Unix /bin/sh interpreter:
+
+REPOS="$1"
+REV="$2"
+USER="$3"
+PROPNAME="$4"
+
+propchange-email.pl "$REPOS" "$REV" "$USER" "$PROPNAME" watchers at example.org
Added: websites/hooks/pre-commit.tmpl
===================================================================
--- websites/hooks/pre-commit.tmpl 2004-07-02 15:18:18 UTC (rev 6946)
+++ websites/hooks/pre-commit.tmpl 2004-07-02 15:31:11 UTC (rev 6947)
@@ -0,0 +1,56 @@
+#!/bin/sh
+
+# PRE-COMMIT HOOK
+#
+# The pre-commit hook is invoked before a Subversion txn is
+# committed. Subversion runs this hook by invoking a program
+# (script, executable, binary, etc.) named 'pre-commit' (for which
+# this file is a template), with the following ordered arguments:
+#
+# [1] REPOS-PATH (the path to this repository)
+# [2] TXN-NAME (the name of the txn about to be committed)
+#
+# The default working directory for the invocation is undefined, so
+# the program should set one explicitly if it cares.
+#
+# If the hook program exits with success, the txn is committed; but
+# if it exits with failure (non-zero), the txn is aborted and no
+# commit takes place. The hook program can use the 'svnlook'
+# utility to help it examine the txn.
+#
+# On a Unix system, the normal procedure is to have 'pre-commit'
+# invoke other programs to do the real work, though it may do the
+# work itself too.
+#
+# *** NOTE: THE HOOK PROGRAM MUST NOT MODIFY THE TXN. ***
+# This is why we recommend using the read-only 'svnlook' utility.
+# In the future, Subversion may enforce the rule that pre-commit
+# hooks should not modify txns, or else come up with a mechanism
+# to make it safe to do so (by informing the committing client of
+# the changes). However, right now neither mechanism is
+# implemented, so hook writers just have to be careful.
+#
+# Note that 'pre-commit' must be executable by the user(s) who will
+# invoke it (typically the user httpd runs as), and that user must
+# have filesystem-level permission to access the repository.
+#
+# On a Windows system, you should name the hook program
+# 'pre-commit.bat' or 'pre-commit.exe',
+# but the basic idea is the same.
+#
+# Here is an example hook script, for a Unix /bin/sh interpreter:
+
+REPOS="$1"
+TXN="$2"
+
+# Make sure that the log message contains some text.
+SVNLOOK=/usr/local/bin/svnlook
+$SVNLOOK log -t "$TXN" "$REPOS" | \
+ grep "[a-zA-Z0-9]" > /dev/null || exit 1
+
+# Check that the author of this commit has the rights to perform
+# the commit on the files and directories being modified.
+commit-access-control.pl "$REPOS" "$TXN" commit-access-control.cfg || exit 1
+
+# All checks passed, so allow the commit.
+exit 0
Added: websites/hooks/pre-revprop-change.tmpl
===================================================================
--- websites/hooks/pre-revprop-change.tmpl 2004-07-02 15:18:18 UTC (rev 6946)
+++ websites/hooks/pre-revprop-change.tmpl 2004-07-02 15:31:11 UTC (rev 6947)
@@ -0,0 +1,49 @@
+#!/bin/sh
+
+# PRE-REVPROP-CHANGE HOOK
+#
+# The pre-revprop-change hook is invoked before a revision property
+# is modified. Subversion runs this hook by invoking a program
+# (script, executable, binary, etc.) named 'pre-revprop-change' (for which
+# this file is a template), with the following ordered arguments:
+#
+# [1] REPOS-PATH (the path to this repository)
+# [2] REVISION (the revision being tweaked)
+# [3] USER (the username of the person tweaking the property)
+# [4] PROPNAME (the property being set on the revision)
+#
+# [STDIN] PROPVAL ** the property value is passed via STDIN.
+#
+# If the hook program exits with success, the propchange happens; but
+# if it exits with failure (non-zero), the propchange doesn't happen.
+# The hook program can use the 'svnlook' utility to examine the
+# existing value of the revision property.
+#
+# WARNING: unlike other hooks, this hook MUST exist for revision
+# properties to be changed. If the hook does not exist, Subversion
+# will behave as if the hook were present, but failed. The reason
+# for this is that revision properties are UNVERSIONED, meaning that
+# a successful propchange is destructive; the old value is gone
+# forever. We recommend the hook back up the old value somewhere.
+#
+# On a Unix system, the normal procedure is to have 'pre-revprop-change'
+# invoke other programs to do the real work, though it may do the
+# work itself too.
+#
+# Note that 'pre-revprop-change' must be executable by the user(s) who will
+# invoke it (typically the user httpd runs as), and that user must
+# have filesystem-level permission to access the repository.
+#
+# On a Windows system, you should name the hook program
+# 'pre-revprop-change.bat' or 'pre-revprop-change.exe',
+# but the basic idea is the same.
+#
+# Here is an example hook script, for a Unix /bin/sh interpreter:
+
+REPOS="$1"
+REV="$2"
+USER="$3"
+PROPNAME="$4"
+
+if [ "$PROPNAME" = "svn:log" ]; then exit 0; fi
+exit 1
Added: websites/hooks/start-commit.tmpl
===================================================================
--- websites/hooks/start-commit.tmpl 2004-07-02 15:18:18 UTC (rev 6946)
+++ websites/hooks/start-commit.tmpl 2004-07-02 15:31:11 UTC (rev 6947)
@@ -0,0 +1,42 @@
+#!/bin/sh
+
+# START-COMMIT HOOK
+#
+# The start-commit hook is invoked before a Subversion txn is created
+# in the process of doing a commit. Subversion runs this hook
+# by invoking a program (script, executable, binary, etc.) named
+# 'start-commit' (for which this file is a template)
+# with the following ordered arguments:
+#
+# [1] REPOS-PATH (the path to this repository)
+# [2] USER (the authenticated user attempting to commit)
+#
+# The default working directory for the invocation is undefined, so
+# the program should set one explicitly if it cares.
+#
+# If the hook program exits with success, the commit continues; but
+# if it exits with failure (non-zero), the commit is stopped before
+# even a Subversion txn is created.
+#
+# On a Unix system, the normal procedure is to have 'start-commit'
+# invoke other programs to do the real work, though it may do the
+# work itself too.
+#
+# Note that 'start-commit' must be executable by the user(s) who will
+# invoke it (typically the user httpd runs as), and that user must
+# have filesystem-level permission to access the repository.
+#
+# On a Windows system, you should name the hook program
+# 'start-commit.bat' or 'start-commit.exe',
+# but the basic idea is the same.
+#
+# Here is an example hook script, for a Unix /bin/sh interpreter:
+
+REPOS="$1"
+USER="$2"
+
+commit-allower.pl --repository "$REPOS" --user "$USER" || exit 1
+special-auth-check.py --user "$USER" --auth-level 3 || exit 1
+
+# All checks passed, so allow the commit.
+exit 0
Added: websites/locks/db-logs.lock
===================================================================
--- websites/locks/db-logs.lock 2004-07-02 15:18:18 UTC (rev 6946)
+++ websites/locks/db-logs.lock 2004-07-02 15:31:11 UTC (rev 6947)
@@ -0,0 +1,7 @@
+DB logs lock file, representing locks on the versioned filesystem logs.
+
+All log manipulators of the repository's
+Berkeley DB environment take out exclusive locks on this file
+to ensure that only one accessor manupulates the logs at the time.
+
+You should never have to edit or remove this file.
Added: websites/locks/db.lock
===================================================================
--- websites/locks/db.lock 2004-07-02 15:18:18 UTC (rev 6946)
+++ websites/locks/db.lock 2004-07-02 15:31:11 UTC (rev 6947)
@@ -0,0 +1,10 @@
+DB lock file, representing locks on the versioned filesystem.
+
+All accessors -- both readers and writers -- of the repository's
+Berkeley DB environment take out shared locks on this file, and
+each accessor removes its lock when done. If and when the DB
+recovery procedure is run, the recovery code takes out an
+exclusive lock on this file, so we can be sure no one else is
+using the DB during the recovery.
+
+You should never have to edit or remove this file.
More information about the commits
mailing list