Re: getting a list of conflicting files

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 You are saying that it does more stuff than that without the -n? That shouldn't happen. As to your other email, I am BasketCase on #rsync. On 08/01/13 02:35, Jonathan Aquilina wrote: > The problem though comes when i remove the n for the dry run and

Re: getting a list of conflicting files

The problem though comes when i remove the n for the dry run and do an actual run it is copying them to the local host On Thu, Aug 1, 2013 at 8:34 AM, Kevin Korb wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > - -e "ssh" is the default so you can drop it if you want. > > the rest i

Re: getting a list of conflicting files

-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 actua

Re: getting a list of conflicting files

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 wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > T

Re: getting a list of conflicting files

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 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-chan

Re: getting a list of conflicting files

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

Re: getting a list of conflicting files

so Rsync would be a better solution in this case? On Thu, Aug 1, 2013 at 8:20 AM, Kevin Korb wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > 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, J

Re: getting a list of conflicting files

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 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 > wrote: >

Re: getting a list of conflicting files

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 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 lsync

Re: getting a list of conflicting files

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 wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > I don't know if conflicting is really the right word but i

Re: getting a list of conflicting files

-BEGIN PGP SIGNED MESSAGE- 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

Re: getting a list of conflicting files

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 wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > It would tell you what rsync would have done without the --dry-ru

Re: getting a list of conflicting files

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 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 ma

getting a list of conflicting files

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 omit

pre 1 OSX errors

Hi Wayne, Trying out 3.1 pre 1 on OSX 10.8.4 I like the new extended stats and the ir-chunk file numbers in log. Also getting a lot of errors and most copies not completing to local disk. rsync just stalls. Standard osx build: patch -p1 https://lists.samba.org/mailman/listinfo/rsync Before po