From: marco-oweber@gmx.de (Marc Weber)
Subject: [sup-talk] Backups ?
Date: Tue, 7 Jul 2009 15:08:44 +0200 [thread overview]
Message-ID: <20090707130844.GA23073@gmx.de> (raw)
Hi, I'd like to setup an automatic backup system cause I don't want to
tag my mails twice and I don't want to loose the information about
archived mails etc.
What do you think about something like this?
Is it enough to keep 4 dumps?
What about moving this code into sup shutdown?
I think everyone wants to have this feature?
run_sup(){
# untested draft
local dump_dir="/var"
sup
sup-dump | bzip2 > "$dump_dir/sup-dumps-`date`"
ls -1t "$dump_dir"/sup-dumps-* | { read; read; read; read; cat } | xargs rm
}
Marc Weber
next reply other threads:[~2009-07-07 13:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-07 13:08 Marc Weber [this message]
2009-07-07 15:26 ` wagnerdm at seas.upenn.edu
2009-07-07 16:10 ` Ben Walton
2009-07-07 16:19 ` Ingmar Vanhassel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090707130844.GA23073@gmx.de \
--to=marco-oweber@gmx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox