From: Tanstaafl <tanstaafl@libertytrek.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Hows this for rsnapshot cron jobs?
Date: Sun, 21 Apr 2013 16:49:10 -0400 [thread overview]
Message-ID: <517450C6.8000309@libertytrek.org> (raw)
In-Reply-To: <51744CF6.80305@gmail.com>
On 2013-04-21 4:32 PM, Alan McKinnon <alan.mckinnon@gmail.com> wrote:
> On 21/04/2013 20:47, Tanstaafl wrote:
>>> 30 20 1 * * root rsnapshot -c /etc/rsnapshot/myhost1.conf monthly
>>> 20 20 1 * * root rsnapshot -c /etc/rsnapshot/myhost1.conf yearly
> Only the last line is wrong - your monthly and yearly are equivalent.To
> be properly yearly, you need a month value in field 4.
Oh, right (I added that interval myself, rsnapshot only comes with the
hourly, daily weekly and monthly by default).
So, if I wanted it to run at 8:20pm on Dec 31, it would be:
20 22 31 12 * root rsnapshot -c /etc/rsnapshot/myhost1.conf yearly
> I'm not familiar with rsnapshot, I assume that package can deal with how
> many of each type of snapshot to retain in it's conf file? I see no
> crons to delete out of date snapshots.
Correct, rsnapshot handles this.
> And, more as a nitpick than anything else, I always recommend that when
> a sysadmin adds a root cronjob, use crontab -e so it goes in
> /var/spool/cron, not /etc/crontab. Two benefits:
>
> - syntax checking when you save and quit
> - if you let portage, package managers, chef, puppet or whatever manage
> your global cronjobs in /etc/portage, then there's no danger that system
> will trash the stuff that you added there manually.
I prefer doing things manually... so, nothing else manages my cron jobs.
That said, I prefer to do this 'the gentoo way'... so is crontab -e the
gentoo way?
;)
next prev parent reply other threads:[~2013-04-21 20:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-21 18:47 [gentoo-user] Hows this for rsnapshot cron jobs? Tanstaafl
2013-04-21 20:32 ` Alan McKinnon
2013-04-21 20:49 ` Tanstaafl [this message]
2013-04-22 7:26 ` Alan McKinnon
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=517450C6.8000309@libertytrek.org \
--to=tanstaafl@libertytrek.org \
--cc=gentoo-user@lists.gentoo.org \
/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