svnadmin is the administrative tool for monitoring and repairing your Subversion repository. For detailed information, see the section called “svnadmin”.
Since svnadmin works via direct repository access (and thus can only be used on the machine that holds the repository), it refers to the repository with a path, not a URL.
--bdb-log-keep(Berkeley DB specific) Disable automatic log removal of database log files. Having these log files around can be convenient if you need to restore from a catastrophic repository failure.
--bdb-txn-nosync(Berkeley DB specific) Disables fsync when
committing database transactions. Used with the
svnadmin create command to create a
Berkeley DB backed repository with
DB_TXN_NOSYNC enabled (which improves
speed but has some risks associated with it).
--bypass-hooksBypass the repository hook system.
--clean-logsRemoves unused Berkeley DB logs.
--force-uuidBy default, when loading data into repository that
already contains revisions, svnadmin
will ignore the UUID from the dump
stream. This option will cause the repository's
UUID to be set to the
UUID from the stream.
--ignore-uuidBy default, when loading an empty repository,
svnadmin will ignore the
UUID from the dump stream. This
option will force that UUID to be ignored (useful for
overriding your configuration file if it has
--force-uuid set).
--incrementalDump a revision only as a diff against the previous revision, instead of the usual fulltext.
--parent-dir
DIRWhen loading a dump file, root paths at
DIR instead of
/.
--revision (-r)
ARGSpecify a particular revision to operate on.
--quietDo not show normal progress—show only errors.
--use-post-commit-hookWhen loading a dump file, run the repository's post-commit hook after finalizing each newly loaded revision.
--use-pre-commit-hookWhen loading a dump file, run the repository's pre-commit hook before finalizing each newly loaded revision. If the hook fails, abort the commit and terminate the load process.