Your message dated Fri, 25 Jul 2008 01:25:53 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#432862: agreed; sorry
has caused the Debian Bug report #432862,
regarding rsnapshot: interval definitions in cron.d unintuitive (particularly
hour)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
432862: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=432862
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: rsnapshot
Version: 1.2.9-1
Severity: normal
The interval definitions in /etc/cron.d/rsnapshot are
unintuitive. I was puzzled why my "hourly" backup was
firing every four hours. Why not defer the definition
to cron by using the built-ins?
-- System Information:
Debian Release: 4.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-4-686
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Versions of packages rsnapshot depends on:
ii logrotate 3.7.1-3 Log rotation utility
ii perl 5.8.8-7 Larry Wall's Practical Extraction
ii rsync 2.6.9-2 fast remote file copy program (lik
Versions of packages rsnapshot recommends:
ii ssh 1:4.3p2-9 Secure shell client and server (tr
-- no debconf information
Use system's definition of hourly/daily/weekly/monthly
Jon Dowland <[EMAIL PROTECTED]>
Thu, 12 Jul 2007 13:20:50 +0100
Index: rsnapshot-1.2.9/debian/cron.d
===================================================================
--- rsnapshot-1.2.9.orig/debian/cron.d 2007-07-12 13:19:09.000000000 +0100
+++ rsnapshot-1.2.9/debian/cron.d 2007-07-12 13:20:10.000000000 +0100
@@ -5,7 +5,7 @@
# To activate this cron file you have to uncomment the lines below.
# Feel free to adapt it to your needs.
-# 0 */4 * * * root /usr/bin/rsnapshot hourly
-# 30 3 * * * root /usr/bin/rsnapshot daily
-# 0 3 * * 1 root /usr/bin/rsnapshot weekly
-# 30 2 1 * * root /usr/bin/rsnapshot monthly
+# @hourly /usr/bin/rsnapshot hourly
+# @daily /usr/bin/rsnapshot daily
+# @weekly /usr/bin/rsnapshot weekly
+# @monthly /usr/bin/rsnapshot monthly
--- End Message ---
--- Begin Message ---
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Johan,
Rsnapshot will move the oldest weekly when running the monthly
backup, the oldest daily when running the weekly, etc. For example,
with the default configuration, where daily is 7 and weekly is 4,
Rsnapshot would move daily.6 into weekly.0 when running the weekly
backup. Thus, the order in which the different intervals are run is
very important: monthly should run before weekly, weekly before
daily, and so forth. In this case, using the different /etc/cron.* is
not suitable.
Finally, regarding the default hourly backup interval, if you want to
retain the last 24 hours of backup you should either change the
hourly interval to 24 and run Rsnapshot hourly, or set up Rsnapshot
to run every 4 hours. In some other situation, when you want to keep
only the last 6 hours of backup, you will want to keep the hourly to
6, and run Rsnapshot every hour. For example, in a business where
most files are changed during business hours, you would keep the
hourly interval to 6, or 8, and configure the hourly job to run
during business hours only, and then the monthly, weekly and daily
during the night.
I am now closing this bug, please do not hesitate to reopen it if you
feel it was closed in error.
Simon
On 19-Jul-08, at 2:21 PM, [EMAIL PROTECTED] wrote:
Hi folks, sorry for the delay -- indeed, I agree with the
reasoning here and my patch was bad. However I also agree
that hourly should be renamed: I think "quadhour" is ok,
how about "quarterdaily"?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (Darwin)
iD8DBQFIiWPl1jAZg9vxR6wRAmBOAJwIJTG0RZaH6JCLlpP0MDyPFVE7JwCfY2tw
XchH391jiRVzChad5fFc+mE=
=gVo/
-----END PGP SIGNATURE-----
--- End Message ---
