Eksempler på bruk av Svnadmin på Engelsk og deres oversettelse til Norsk
{-}
-
Colloquial
-
Ecclesiastic
-
Ecclesiastic
-
Computer
The syntax of svnadmin is similar to that of svnlook.
If a log message needs to be changed by an administrator,this can be done using svnadmin setlog.
The svnadmin program is the repository administrator's best friend.
Using your current version of svnadmin, dump your repositories to dump files.
Svnadmin upgrade: fix data loss when cancelling in last stage(r1494298).
If so, the transaction's name can be passed to svnadmin rmtxns, which will perform the cleanup of the transaction.
Svnadmin setlog can be called in a way that bypasses the hook interface altogether.
Explains in great detail every subcommand of svn, svnadmin, and svnlook with plenty of examples for the whole family!
Move your old repositories out of the way, andcreate new empty ones in their place using your new svnadmin.
We have already mentioned svnadmin's create subcommand(see the section called“Repository Creation and Configuration”).
But an administrator can get around these protections by passing the--bypass-hooks option to the svnadmin setlog command.
By using the--parent-dir option of svnadmin load, you can specify a new virtual root directory for the load process.
Also, changes made to DB_CONFIG won't take effect until you recover the database environment(using svnadmin recover).
If you do indeed want to remove a transaction,its name can be passed to svnadmin rmtxns, which will perform the cleanup of the transaction.
While svnadmin dump has a consistent leading slash policy(to not include them), other programs that generate dump data might not be so consistent.
We will also talk about repository maintenance,including the use of the svnlook and svnadmin tools(which are provided with Subversion).
You use the svnadmin dump command to generate the dump data, and svnadmin load to populate a new repository with it(see sezione chiamata«Migrating a Repository»).
All data is dumped in the format that can be read an written by svnadmin load/dump, so the data which is produced can easily be imported….
Note that svnadmin dump is reading revision trees from the repository just like any other“reader” process would(e.g., svn checkout), so it's safe to run this command at any time.
We discussed in an earlier section of this chapter how to use svnadmin dump--incremental to perform an incremental backup(see sezione chiamata«Migrating a Repository»).
Note that svnadmin dump is reading revision trees from the repository just like any other«reader» process would(svn checkout, for example). So it's safe to run this command at any time.
The examples used in this appendix assume that you have svn,the Subversion command-line client, and svnadmin, the administrative tool, ready to go on a Unix-like operating system.
The other subcommand in the pair, svnadmin load, parses the standard input stream as a Subversion repository dump file and effectively replays those dumped revisions into the target repository for that operation.
While some parts of a Subversion repository- such as the configuration files and hook scripts- are meant to be examined and modified manually,you shouldn't(and shouldn't need to) tamper with the other parts of the repository“by hand.” The svnadmin tool should be sufficient for any changes necessary to your repository, or you can look to third-party tools for tweaking relevant subsections of the repository.
You may have noticed that the path argument to svnadmin was just a regular filesystem path and not a URL like the svn client program uses when referring to repositories.
Both svnadmin and svnlook are considered server-side utilities- they are used on the machine where the repository resides to examine or modify aspects of the repository, and are in fact unable to perform tasks across a network.
If you add the--incremental option when you dump your repository, svnadmin will compare the first dumped revision against the previous revision in the repository- the same way it treats every other revision that gets dumped.
For example, svnadmin list-unused-dblogs and svnadmin list-dblogs perform a subset of what is provided by the Berkeley db_archive command, and svnadmin recover reflects the common use cases of the db_recover utility.
To ensure that the output of each execution of svnadmin dump is self-sufficient, the first dumped revision is by default a full representation of every directory, file, and property in that revision of the repository.
Note that because svnadmin uses standard input and output streams for the repository dump and load process, people who are feeling especially saucy can try things like this(perhaps even using different versions of svnadmin on each side of the pipe).