From: Arne Jansen <sensille@gmx.net>
To: "Fajar A. Nugraha" <list@fajar.net>
Cc: Anand Jain <Anand.Jain@oracle.com>, cwillu <cwillu@cwillu.com>,
linux-btrfs@vger.kernel.org, hugo@carfax.org.uk,
chris.mason@oracle.com
Subject: Re: [PATCH] [RFC] Add btrfs autosnap feature
Date: Mon, 05 Mar 2012 08:18:28 +0100 [thread overview]
Message-ID: <4F5468C4.5090401@gmx.net> (raw)
In-Reply-To: <CAG1y0sdy0p2D4AHBcHgiYxPYknbW8O3xgCuvwKy==sWnW5BJAg@mail.gmail.com>
On 05.03.2012 08:07, Fajar A. Nugraha wrote:
> On Mon, Mar 5, 2012 at 1:51 PM, Anand Jain <Anand.Jain@oracle.com> wrote:
>>
>>> (notably the direct modification of
>>> crontab files, which is considered to be an internal detail if I
>>> understand correctly, and I'm fairly certain is broken as written),
>>
>>
>> I did came across that point of view however, using crontab cli in the
>> program wasn't convincing either, (library call would have been better).
>> any other better ways to manage cron entries ?
>>
>
> /etc/cron.{d,daily,hourly} ?
>
An alternative would be to have an hourly (or minutely) fixed cronjob
and let the tool decide whether any snapshots have to be created. This
way you don't have to mess around with the crontab.
next prev parent reply other threads:[~2012-03-05 7:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-29 2:59 [RFC] [PATCH] Add btrfs autosnap feature asj
2012-02-29 2:59 ` [PATCH] [RFC] " asj
2012-02-29 3:38 ` Anand Jain
2012-03-01 11:54 ` cwillu
2012-03-02 11:34 ` Arvin Schnell
2012-03-02 12:04 ` cwillu
2012-03-02 12:25 ` Sander
2012-03-05 6:51 ` Anand Jain
2012-03-05 7:07 ` Fajar A. Nugraha
2012-03-05 7:18 ` Arne Jansen [this message]
2012-03-05 10:21 ` Anand Jain
2012-03-05 10:28 ` cwillu
2012-03-01 13:23 ` Roman Mamedov
2012-03-06 7:56 ` [PATCH 1/2] Make find_updated_files to return value instead of printing Anand jain
2012-03-06 7:56 ` [PATCH 2/2] Use transaction id to determin if there is any change in the subvol Anand jain
2012-03-06 9:07 ` [PATCH 2/2 v2] " Anand jain
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=4F5468C4.5090401@gmx.net \
--to=sensille@gmx.net \
--cc=Anand.Jain@oracle.com \
--cc=chris.mason@oracle.com \
--cc=cwillu@cwillu.com \
--cc=hugo@carfax.org.uk \
--cc=linux-btrfs@vger.kernel.org \
--cc=list@fajar.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.