Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
backupninja
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Custom issue tracker
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Deploy
Releases
Model registry
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Liberate
backupninja
Commits
929a6bda
Commit
929a6bda
authored
17 years ago
by
micah
Browse files
Options
Downloads
Patches
Plain Diff
actually include the example file
parent
f11befa7
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
examples/Makefile.am
+1
-1
1 addition, 1 deletion
examples/Makefile.am
examples/example.maildir
+53
-0
53 additions, 0 deletions
examples/example.maildir
with
54 additions
and
1 deletion
examples/Makefile.am
+
1
−
1
View file @
929a6bda
EXAMPLES
=
example.dup example.ldap example.makecd example.mysql
\
example.pgsql example.rdiff example.sh example.rsync
\
example.svn example.sys example.trac
example.svn example.sys example.trac
example.maildir
EXTRA_DIST
=
$(
EXAMPLES
)
...
...
This diff is collapsed.
Click to expand it.
examples/example.maildir
0 → 100644
+
53
−
0
View file @
929a6bda
##
## This is an example maildir configuration file.
##
## The maildir handler slowly creates a backup of each user's
## maildir to a remote server. It is designed to be run with
## low overhead in terms of CPU and bandwidth, so it runs pretty
## slow. Hardlinking is used to save storage space. The actual
## maildir is stored within each snapshot directory.
##
## The basic algorithm is to rsync each maildir individually,
## and to use hard links for retaining historical data.
##
## We handle each maildir individually because it becomes very
## unweldy to hardlink and rsync many hundreds of thousands
## of files at once. It is much faster to take on smaller
## chunks at a time.
##
## Any maildir which is deleted from the source will be moved to
## "deleted" directory in the destination. It is up to you to
## periodically remove this directory or old maildirs in it.
## The defaults are useful in most cases, just make sure
## to configure the source and destination information
when = everyday at 21:00
## each users maildir will contain these files:
## daily.1, daily.2, daily.3, daily.4, daily.5, weekly.1, weekly.2,
## weekly.3, monthly.1
## if keepdaily is 5, keepweekly is 3, and keepmonthly is 1
keepdaily = 5
keepweekly = 3
keepmonthly = 1
# directory which contains all the maildirs
# this directory is expected to have subdirectories lettered a-z and
# in each letter subdirectory are the users Maildirs which start with
# those letters
srcdir = /maildir/riseup.net
# put the backups under this directory
destdir = /crypta/maildir/riseup.net
desthost = kakapo-pn
# For the backup rotation to work, destuser must be able to run
# arbitrary bash commands on the desthost.
destuser = backer
# remove any maildirs from backup which might have been deleted
remove = yes
# use a ssh-mux to reuse connections, see the following article
# http://www.debian-administration.org/articles/290 for an example
multiconnection = notset
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment