getting a list of conflicting files

[Kevin Korb]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

- -e "ssh" is the default so you can drop it if you want.

the rest is pretty much what I said I just spelled them out so they
would be easier to lookup.  You can also add a --delete if you want to
see what is missing the dry run prevents it from actually deleting
anything.

On 08/01/13 02:32, Jonathan Aquilina wrote:
> my switches are -ain at this point the problem though is its
> working but copying them to the same host. I need to test copying
> to a remote host
> 
> rsync -ain -e "ssh" "$LOCALDIR" "$REMOTEDIR"
> 
> 
> On Thu, Aug 1, 2013 at 8:29 AM, Kevin Korb <kmk at sanitarium.net 
> <mailto:kmk at sanitarium.net>> wrote:
> 
> That is only showing new files in a new directory.  The rest
> depends on the rest of your command line.  For instance if you had 
> --ignore-existing you would never see a changed file.  For a 
> difference list I would probably use --archive --itemize-changes 
> --dry-run and probably not much else.
> 
> On 08/01/13 02:24, Jonathan Aquilina wrote:
>> this is what im getting currently as a test im running
> 
>> cd+++++++++ syncDir/
>>> f+++++++++ syncDir/rsync-3.0.6-1.aix5.3.ppc.rpm f+++++++++ 
>>> syncDir/vim-common-6.3-1.aix5.1.ppc.rpm f+++++++++ 
>>> syncDir/vim-enhanced-6.3-1.aix5.1.ppc.rpm
> 
>> does this mean that nothing has changed?
> 
> 
> 
>> On Thu, Aug 1, 2013 at 8:22 AM, Kevin Korb <kmk at sanitarium.net
> <mailto:kmk at sanitarium.net>
>> <mailto:kmk at sanitarium.net <mailto:kmk at sanitarium.net>>> wrote:
> 
>> If you are just looking for a list of what is different then
>> yes.
> 
>> On 08/01/13 02:21, Jonathan Aquilina wrote:
>>> so Rsync would be a better solution in this case?
> 
>>> On Thu, Aug 1, 2013 at 8:20 AM, Kevin Korb <kmk at sanitarium.net
> <mailto:kmk at sanitarium.net>
>> <mailto:kmk at sanitarium.net <mailto:kmk at sanitarium.net>>
>>> <mailto:kmk at sanitarium.net <mailto:kmk at sanitarium.net>
> <mailto:kmk at sanitarium.net <mailto:kmk at sanitarium.net>>>> wrote:
> 
>>> lsyncd is for real time syncing.  Whenever something gets 
>>> changed it would spawn an rsync to update the other copy.
> 
>>> On 08/01/13 02:18, Jonathan Aquilina wrote:
>>>> At this point im debating if rsync is the right tool. I am 
>>>> trying to determine if lsyncd which is based on rsync would
>>>> do the trick.
> 
> 
>>>> On Thu, Aug 1, 2013 at 8:15 AM, Kevin Korb
>>>> <kmk at sanitarium.net
> <mailto:kmk at sanitarium.net>
>> <mailto:kmk at sanitarium.net <mailto:kmk at sanitarium.net>>
>>> <mailto:kmk at sanitarium.net <mailto:kmk at sanitarium.net>
> <mailto:kmk at sanitarium.net <mailto:kmk at sanitarium.net>>>
>>>> <mailto:kmk at sanitarium.net <mailto:kmk at sanitarium.net>
> <mailto:kmk at sanitarium.net <mailto:kmk at sanitarium.net>>
>> <mailto:kmk at sanitarium.net <mailto:kmk at sanitarium.net>
> <mailto:kmk at sanitarium.net <mailto:kmk at sanitarium.net>>>>> wrote:
> 
>>>> 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 sanitarium.net <mailto:kmk at sanitarium.net>
>> <mailto:kmk at sanitarium.net <mailto:kmk at sanitarium.net>>
>>> <mailto:kmk at sanitarium.net <mailto:kmk at sanitarium.net>
> <mailto:kmk at sanitarium.net <mailto:kmk at sanitarium.net>>>
>>>> <mailto:kmk at sanitarium.net <mailto:kmk at sanitarium.net>
> <mailto:kmk at sanitarium.net <mailto:kmk at sanitarium.net>>
>> <mailto:kmk at sanitarium.net <mailto:kmk at sanitarium.net>
> <mailto:kmk at sanitarium.net <mailto:kmk at sanitarium.net>>>>
>>>>> <mailto:kmk at sanitarium.net <mailto:kmk at sanitarium.net>
> <mailto:kmk at sanitarium.net <mailto:kmk at sanitarium.net>>
>> <mailto:kmk at sanitarium.net <mailto:kmk at sanitarium.net>
> <mailto:kmk at sanitarium.net <mailto:kmk at sanitarium.net>>>
>>> <mailto:kmk at sanitarium.net <mailto:kmk at sanitarium.net>
> <mailto:kmk at sanitarium.net <mailto:kmk at sanitarium.net>>
>> <mailto:kmk at sanitarium.net <mailto:kmk at sanitarium.net>
> <mailto:kmk at sanitarium.net <mailto:kmk at sanitarium.net>>>>>> 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: 
>>>>> https://lists.samba.org/mailman/listinfo/rsync Before 
>>>>> posting, read: 
>>>>> http://www.catb.org/~esr/faqs/smart-questions.html
> 
> 
> 
> 
>>>>> -- Jonathan Aquilina
> 
> 
> 
> 
> 
>>>> -- Jonathan Aquilina
> 
> 
> 
> 
> 
>>> -- Jonathan Aquilina
> 
> 
> 
> 
> 
>> -- Jonathan Aquilina
> 
> 
> 
> 
> 
> -- Jonathan Aquilina

- -- 
~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~
	Kevin Korb			Phone:    (407) 252-6853
	Systems Administrator		Internet:
	FutureQuest, Inc.		Kevin at FutureQuest.net  (work)
	Orlando, Florida		kmk at sanitarium.net (personal)
	Web page:			http://www.sanitarium.net/
	PGP public key available on web site.
~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.20 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlH6AWoACgkQVKC1jlbQAQdmGgCgp4F+TuPR+Gynv77aV8Xh5yFp
3sYAniW32mqTiA4hxjFBqEOgTE+0HP/g
=Z835
-----END PGP SIGNATURE-----