From: x y <x1y2w3@gmail.com>
To: cygwin@cygwin.com
Subject: Re: tar incremental backups and ctime problem
Date: Mon, 23 May 2016 08:54:00 -0000 [thread overview]
Message-ID: <CAOKAGPOzSYkmFRJazgQMwjUCKsKaBbE9gcVAdNnNvYUkmc=9Bw@mail.gmail.com> (raw)
In-Reply-To: <9fdf98cf-e3d1-e453-1c98-2c206afe81c9@gmail.com>
Hi Marco,
Thanks for your reply. The problem is that there are a lot of files to
be checked so replacing ctime by time to support tar incremental
backup should be more practical.
On Mon, May 23, 2016 at 11:46 AM, Marco Atzeri <marco.atzeri@gmail.com> wrote:
> On 23/05/2016 10:40, x y wrote:
>>
>> Hello,
>>
>> The MS Office applications are changing the ctime value of .doc and
>> .xls files even if they are not modified. Opening and closing an
>> office file without modifying the content is changing ctime and the
>> unmodified document is included in the incremental tar archive. Could
>> it be possible to use the mtime value instead of ctime to avoid the
>> the reappearance of the unchanged files in the incremental archive?
>>
>> Test OS : Windows 7 Sp1
>>
>
>
> find -ctime should be able you to build the list of files
> that are changed and that tar should process
>
> Regards
> Marco
>
> --
> Problem reports: http://cygwin.com/problems.html
> FAQ: http://cygwin.com/faq/
> Documentation: http://cygwin.com/docs.html
> Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
>
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2016-05-23 8:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-23 8:40 x y
2016-05-23 8:47 ` Marco Atzeri
2016-05-23 8:54 ` x y [this message]
2016-05-23 9:06 ` Marco Atzeri
2016-05-23 9:18 ` x y
2016-05-23 14:29 ` Eric Blake
2016-05-23 14:57 ` x y
2016-05-23 15:24 ` Vince Rice
2016-05-23 15:35 ` Marco Atzeri
2016-05-23 16:56 ` x y
2016-05-23 19:02 ` Eric Blake
2016-05-23 17:19 ` Erik Soderquist
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='CAOKAGPOzSYkmFRJazgQMwjUCKsKaBbE9gcVAdNnNvYUkmc=9Bw@mail.gmail.com' \
--to=x1y2w3@gmail.com \
--cc=cygwin@cygwin.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).