summaryrefslogtreecommitdiff
path: root/app-backup/vzdump/metadata.xml
diff options
context:
space:
mode:
authorV3n3RiX <venerix@redcorelinux.org>2018-07-14 20:56:41 +0100
committerV3n3RiX <venerix@redcorelinux.org>2018-07-14 20:56:41 +0100
commitd87262dd706fec50cd150aab3e93883b6337466d (patch)
tree246b44c33ad7a57550430b0a60fa0df86a3c9e68 /app-backup/vzdump/metadata.xml
parent71bc00c87bba1ce31de0dac6c3b7fd1aee6917fc (diff)
gentoo resync : 14.07.2018
Diffstat (limited to 'app-backup/vzdump/metadata.xml')
-rw-r--r--app-backup/vzdump/metadata.xml12
1 files changed, 0 insertions, 12 deletions
diff --git a/app-backup/vzdump/metadata.xml b/app-backup/vzdump/metadata.xml
deleted file mode 100644
index da366eec9b75..000000000000
--- a/app-backup/vzdump/metadata.xml
+++ /dev/null
@@ -1,12 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
-<pkgmetadata>
- <!-- maintainer-needed -->
- <longdescription lang="en">
- vzdump is a utility to make consistent snapshots of running OpenVZ VEs. It basically creates a tar archive of the VE private area, which also includes the VE configuration files.
- There are several ways to provide consistency:
- - stop the VE during backup (very long downtime)
- - use rsync and suspend/resume (minimal downtime)
- - use LVM2 (no downtime)
- </longdescription>
-</pkgmetadata>