getting a list of conflicting files

Kevin Korb kmk at
Thu Aug 1 00:15:05 MDT 2013

Hash: SHA1

I don't know if conflicting is really the right word but it is a list
of differences.  I wouldn't bother with the snapshot unless you are
going to process the list and then do the real sync.

On 08/01/13 02:10, Jonathan Aquilina wrote:
> I was thinking of using an lvm snapshot. all i really need is just
> a list of the conflicting files to be emailed in a report.
> On Thu, Aug 1, 2013 at 8:02 AM, Kevin Korb <kmk at 
> <mailto:kmk at>> wrote:
> It would tell you what rsync would have done without the --dry-run
> and why it would have done it.  But it can't guarantee that nothing
> will change between the dry run and the real run.  Of course if
> your source is a snapshotted filesystem that won't matter.
> On 08/01/13 01:59, Jonathan Aquilina wrote:
>> I am in the process of writing a script on some testing machines 
>> and I am wondering if having it perform a dry run and itemized
>> the items if it would provide a list of differences such as file
>> size and name etc conflicts
>> -- Jonathan Aquilina
> -- Please use reply-all for most replies to avoid omitting the
> mailing list. To unsubscribe or change options: 
> Before posting,
> read:
> -- Jonathan Aquilina

- -- 
	Kevin Korb			Phone:    (407) 252-6853
	Systems Administrator		Internet:
	FutureQuest, Inc.		Kevin at  (work)
	Orlando, Florida		kmk at (personal)
	Web page:
	PGP public key available on web site.
Version: GnuPG v2.0.20 (GNU/Linux)
Comment: Using GnuPG with Thunderbird -


More information about the rsync mailing list