On Fri, 2008-07-04 at 21:55 -0400, Crawford Kyle wrote:
> I'd like to see the create times and fileflags patches included so all
> metadata tests pass with backup bouncer 'out of the box' on Mac OS X.
Those patches are Mac-specific, so I'm pretty sure they won't go into
the main rsync, but it wo
On Jul 4, 2008, at 7:01 PM, Wayne Davison wrote:
Other things in the patches dir, suggestions made here, and
enhancement
requests from bugzilla will all be reviewed for possible inclusion.
I'd like to see the create times and fileflags patches included so all
metadata tests pass with bac
Wayne Davison wrote:
On Fri, Jul 04, 2008 at 02:59:20PM -0400, Brian Lindholm wrote:
it would be even better if it only rewrote the portions of large files
that had actually changed instead of resending the entire file.
You can use --no-whole-file with --inplace (since rsync's default update
me
I think it's about time to start adding some new features to rsync 3
instead of just making bug fixes, so I'm planning to starting work on
version 3.1.0. This will start the use of a new version numbering
idiom where feature releases increment the sub-version number, while
patch releases continue
On Fri, Jul 04, 2008 at 02:59:20PM -0400, Brian Lindholm wrote:
> it would be even better if it only rewrote the portions of large files
> that had actually changed instead of resending the entire file.
You can use --no-whole-file with --inplace (since rsync's default update
method is to write out
On Fri, Jul 04, 2008 at 05:08:41PM -0400, Matt McCutchen wrote:
> Use --recursive and then exclude the stuff you don't want, e.g.,
> --exclude='/*/' to exclude all subdirectories.
You can also use -d (--dirs) instead of -r (--recursive). That makes
rsync transfer just the contents of a specified
On Fri, 2008-07-04 at 20:11 +0100, Tiago Marques wrote:
> In the past, since
> --delete-before did nothing, I did a dry run and then parsed the
> output to have it "rm" the files that were to be deleted. That so also
> because the --delete needs the --recursive option, which for me is
> very imprac
Is there a way to force rsync to perform delta-transfers even on local
drive-to-drive copies?
The reason I ask is that I've started using a USB flash drive as a
medium for "poor man's off-site backup". Rsync does a beautiful job on
avoiding overwrites of unchanged files, but it would be even
https://bugzilla.samba.org/show_bug.cgi?id=3784
--- Comment #4 from [EMAIL PROTECTED] 2008-07-04 15:55 CST ---
Oh, forgot to mention, but that patch should apply to v3.0.3.
--
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
--- You are receiving this mail
https://bugzilla.samba.org/show_bug.cgi?id=3784
--- Comment #3 from [EMAIL PROTECTED] 2008-07-04 15:54 CST ---
Created an attachment (id=3390)
--> (https://bugzilla.samba.org/attachment.cgi?id=3390&action=view)
patch to give total run progress indication
Here's a little patch that c
On Fri, Jul 04, 2008 at 08:11:36PM +0100, Tiago Marques wrote:
> rsync --delete-before -v -tvlpr
> rsync://rsync.sabayonlinux.org/SabayonLinux/* ./ --dry-run
Check out the manpage on the --delete option. The very first paragraph
tells you why you shouldn't be using a wildcard (*) there:
ht
Inside the target dir, there is a file named "asdasdasd" which isn't
deleted, nor mentioned to, since this is a dry-run.
with:
rsync --delete-before -v -tvlpr
rsync://rsync.sabayonlinux.org/SabayonLinux/* ./ --dry-run
i get:
-
On Fri, 2008-07-04 at 16:13 +0100, Tiago Marques wrote:
> I had this working on an older version, since 2.6.9 that when I set
> --delete and --dry-run, I get no "Deleting **" lines.
Be sure to pass -v because, since rsync 2.6.7, --dry-run no longer
implies it:
http://gitweb.samba.org/?p=rsync
https://bugzilla.samba.org/show_bug.cgi?id=3784
[EMAIL PROTECTED] changed:
What|Removed |Added
CC||[EMAIL PROTECTED]
--- Comment #2
I had this working on an older version, since 2.6.9 that when I set
--delete and --dry-run, I get no "Deleting **" lines. Also, the
--delete-before never worked for me.
Working on a space constrained mirror, this has proven very handy,
when it works. What's up with the new versions? I haven't c
Problem solved by updating to rsync 3.0.3
Cheers,
Axel.
2008/6/12 Axel Rose <[EMAIL PROTECTED]>:
> Hello all,
>
> I have trouble to use rsync (tested with 3.0.2 and 3.0.3pre2) on MacOS X
> 10.3.
> Rsync always seems to stop when working on open files (?). Source is my
> laptop
> hard disk, desti
Thanks a lot, now it works.
br
Matt McCutchen-7 wrote:
>
> On Thu, 2008-07-03 at 01:58 -0700, stratton wrote:
>> >Are you sure? Please post your daemon configuration and "ls -l" output
>> >for the affected destination files.
>>
>> the destination files all belong to the rsyncd user as i mad
On Fri, Jul 04, 2008 at 10:08:49AM +0200, [EMAIL PROTECTED] wrote:
> Does anyone have an idea how to "change" to a directory on remote maschine
> to use relative paths (-R) ?
Starting with 2.6.7 you can insert a dot dir into any source path to
indicate where the duplicating of directories starts:
https://bugzilla.samba.org/show_bug.cgi?id=5583
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |ASSIGNED
Summary|Files alway
Hi Developers,
i have a problem with syncing relative paths (-r) on remote host.
Using relative paths the local way does function perfectly, because you
are able to change the directory before synchronisation.
Example:
cd pathToRelativePaths;
rsync -R -e "." localpath1/ localpath2/ [EM
20 matches
Mail list logo
