Kevin Korb schrieb:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I am not much of a programmer so I know I could never take over rsync
development but if I could boss such people around here are the new
directions I would take:
1. --itmize-changes is eliminated and becomes part of --verbose
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Yeah, I know that there is an inherent resistance to changing behavior
but IMO --verbose is utterly useless without --itemize-changes. There
is simply no reason to provide a list of transferred file names and
nothing else about them.
I am not much of
> First, you should almost always use -t unless you have a really good
> reason to not sync timestamps otherwise future rsync runs will not
> know what has changed and what hasn't.
Sure, thats my default.
> Finally, when in doubt, --itemize-changes.
This was the right hint, thanks ;) rsync doesn
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
First, you should almost always use -t unless you have a really good
reason to not sync timestamps otherwise future rsync runs will not
know what has changed and what hasn't.
Second, when you run with -p rsync should detect and fix any
permission diff
Hi,
is rsync supposed to detect permission change only (if other attributes are
equal at
both source and target)?
I'm able to synchronize permissions by -p when the file changes (e.g. its
timestamp when -t is used) but otherwise the sole permission change of
the file (e.g. via chmod u-w file) re
On Mar 1, 2012, at 21:52, Kevin Korb wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Is it actually not doing anything? It should only list files that it
> is actually doing something with unless you use more than one -v. Try
> adding --itemize-changes to find out (-v is fairly us
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Is it actually not doing anything? It should only list files that it
is actually doing something with unless you use more than one -v. Try
adding --itemize-changes to find out (-v is fairly useless without it
anyway).
Also, don't use -z unless you a
Thanks to all for jumping in on this one. I've used rsync in a kind of offhand
manner for years, only now was it necessary to "get serious" with it
So then, using -a **includes** -r? Goodness me, I was using -ra so who knows
what gnarliness I was actually causing!!
If I can briefly say what
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Yes, -a includes -r and a bunch of other things.
- --no-i-r disables the incremental recursion and forces rsync to hold
the entire tree in memory in addition to fully scanning the tree on
both ends before copying anything.
On 03/01/12 14:39, Elliot W
On Mar 1, 2012, at 11:34 AM, Kevin Korb wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Without -r rsync will ignore all directories even if the path you
> specified is a directory. That is what recursive means.
>
> If you are having memory usage issues make sure you are running rs
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Without -r rsync will ignore all directories even if the path you
specified is a directory. That is what recursive means.
If you are having memory usage issues make sure you are running rsync
version 3 on both ends and check that you aren't using any
Without the -r switch, I believe that rsync will ignore directory trees. Very
often, I think rsync is run with -a, which includes -r, so it's easy to miss
this fact.
If you want to reduce memory/processor demand, I think that
-r --no-i-r
may help.
On Mar 1, 2012, at 6:29 AM, Colin Raven wrot
On Thu, Mar 1, 2012 at 4:26 AM, Daniel Bolgheroni wrote:
> Is it possible to use rsync to check if there are changes in the files
> I'm trying to sync, but just to check?
>
Someone already suggested --itemize-changes, so I'll just mention that if
you want to check file content (to avoid a false-p
Google hasn't been a whole lot of help here, so here goes...
Using the -r switch appears to impose a significant performance hit on
low[er] end (embedded) systems, i.e. those without scads of memory, and/or
multi-core workstation or server class machines. If you DON'T specify the
-r switch, surely
On Thu 01 Mar 2012, Daniel Bolgheroni wrote:
>
> I'm willing to use -anv (-n for --dry-run) and parse the output. But
> maybe there is an easier way? Maybe some status returned given a
> specific set of parameters?
I'd use -i (itemize changes) instead of -v as that's probably easier to
parse in a
Hi rsync@,
Is it possible to use rsync to check if there are changes in the files I'm
trying to sync, but just to check?
I need to check if the files I have in a local directory differs from
the files in an anonymous rsync server.
I'm willing to use -anv (-n for --dry-run) and parse the output.
https://bugzilla.samba.org/show_bug.cgi?id=8177
--- Comment #8 from Rick 2012-03-01 10:08:28 UTC ---
Hi Jorge,
You're not alone :)
I'm using rsync the backup some vmware servers. Small files work without any
problems but the large (-flat.vmdk) file only works the first time. (I do
create a snaps
17 matches
Mail list logo
