Displaying 20 results from an estimated 1000 matches similar to: "rsync 2.6.1 released (including security note)"
2001 Aug 06
1
merge rsync+ into rsync (was Re: rsync-2.4.7 NEWS file)
> Just curious: what about the rsync+ patch?
Thanks for the reminder.
I've just committed Jos's rsync+ patch onto the
"branch_mbp_rsyncplus_merge" branch. If it works OK and nobody
screams I will move it across onto the main tree tomorrow or
Wednesday.
I see the patch doesn't add documentation about the new options to the
man page, so we should fix that in the future.
2006 Apr 26
2
--link-dest and file/dir transfer to remote rsync daemon
Hi NG,
I want to do incremental backups to a remote server running rsyncd
(because daemonless transfer via ssh often hangs!). In contrast to
transfer via ssh (without remote rsyncd) this doesn't seem possible, or
do I miss something?
Imagine I want to incrementally backup `mydir' to the backup space
`backup' on e remote server `alpha' running an rsync daemon. rsyncd on
2004 Jan 30
1
rsync 2.6.0: possible sanitization bug?
Hiya.
While merging the 2.6.0 changes into our modified version of rsync, I
noticed the following bit of code in 2.6.0's options.c:
extern int sanitize_paths;
if (sanitize_paths)
sanitize_path(strdup(files_from), NULL);
filesfrom_fd = open(files_from, O_RDONLY|O_BINARY);
Since sanitize_path modifies its first argument in place, the path that
open()
2002 Aug 02
1
[patch] --link-dest
Updated to current cvs without the --exclude-from - patch.
This patch allows specifying a --link-dest path similar to
--compare-dest except that unchanged files are hard-linked to the
--link-dest path instead of producing a sparse tree.
--
________________________________________________________________
J.W. Schultz Pegasystems Technologies
email address: jw@pegasys.ws
Remember
2002 Aug 05
5
[patch] read-devices
Greetings,
I'd like to propose a new option to rsync, which causes it to read
device files as if they were regular files. This includes pipes,
character devices and block devices (I'm not sure about sockets). The
main motivation is cases where you need to synchronize a large amount of
data that is not available as regular files, as in the following scenarios:
* Keep a copy of a block
2004 Feb 20
1
[patch] fix for "refuse options" ignored due to popt
Hello,
I found the reason why "refuse options" is ignored on the server
side. When then 5th argument (int val) in the poptOption struct is
set to zero, the parsing function poptGetNextOpt() just continues
with the next arg, without returning. So check_refuse_options() is
simply not called in such cases.
The attached patch makes "refuse options" work with checksum and
2003 Jul 29
1
"-b --suffix '' --delete --backup-dir /path/" combination does not act as expected
Skipped content of type multipart/mixed-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.samba.org/archive/rsync/attachments/20030728/49616c2f/attachment.bin
2004 Apr 07
2
--suffix problem - possibly bug?
I'm having an issue with the --suffix and -b flags -
I've tried the following commands:
rsync -avbr --backup-dir=/rsyncbackup rsynctest user@server.com::module
rsync -avbr --backup-dir=/rsyncbackup --suffix="" rsynctest
user@server.com::module
and either way, I wind up with a tilde as a suffix on all the files
moved into the backup directory at time of synchronization.
2004 Jul 12
2
[PATCH] Batch-mode rewrite
Wayne,
Please consider the attached patch. This applies to the current
CVS, and is independant of patches/local-batch.diff. As a matter of
fact, I'm sure it would conflict heavily with local-batch.diff.
This version of batch mode has a couple distinguishing features:
Write-batch records (almost) the entire sender side of the conversation
into one file. ("Almost" because it has
2010 Jun 15
3
about rsyncing of block devices
Hiya,
I can see it's a regular subject on this list.
I, like others wanted to use rsync to synchronise two block
devices (as it happens one lvm volume and one nbd device served
by qemu-img on a remote host from a qcow2 disk image so that I
can keep the old versions)
As I couldn't find any report of it being done successfully,
I'm just sharing my findings as it might benefit others.
2015 Jan 16
3
wrong transfer of app packages using --backup
Dear All,
I have been seeing some strange behavior using rsync 3.1.1 on OSX with the 3 standard patches applied when using the --backup and --backup-Dir options.
This works as expected on 3.0.9, moving any files on dest that are not on source to the backup folder. If no changes then the backup folder is not even created.
-aHAXN --fileflags --force-change --protect-decmpfs ?delete --backup
2002 Mar 08
1
[PATCH][RFC] space saving incrementals
Please CC me directly as i'm not on the list.
I have attached a patch against latest CVS (cvs diff -u)
that adds the following functionality. I can break it up if
you would prefer it in pieces. Comments welcome.
o add compare-perms option
This creates a new inode for a file even if only
the perms have changed. This way if a file
outside of destdir is hardlinked to a dentry
inside
2004 Aug 02
4
reducing memmoves
Attached is a patch that makes window strides constant when files are
walked with a constant block size. In these cases, it completely
avoids all memmoves.
In my simple local test of rsyncing 57MB of 10 local files, memmoved
bytes went from 18MB to zero.
I haven't tested this for a big variety of file cases. I think that this
will always reduce the memmoves involved with walking a large
2019 Mar 22
2
Kudos and feature question
Kudos all that maintain this awesome and enduring piece of software. Awesome job, many thanks.
I’ve come across a use case that would greatly benefit form a —delete-older-than <secs> argument. This would behave the same as —delete only sparing files dest that have a creating time less than <secs> ago. How hard would this be to implement? Where would I start ?
TIA,
Francois
2003 Apr 25
1
suggest warning for nonexistant compare_dest
Hello rsync developers,
The string compare_dest (in options.c) is set whenever the --compare-dest
or --link-dest options is called. However, if the directory specified by
compare_dest does not exist, then the target files (which should have been
in compare_dest) are not found, and every transfer is a full transfer.
I can't imagine that would ever be the user's intent. Perhaps a
2003 Mar 22
2
[RFC] protocol version
I'm in the midst of coding a patch set for consideration
that will bump the protocol version and have a couple of
observations.
The current minimum backwards-compatible protocol is 15
but we have code that checks for protocol versions as old as
12. If someone else doesn't beat me to it i'm considering
cleaning out the pre-15 compatibility code. A backwards
compatibility patch could
2005 Nov 01
2
request: add TCP buffer options to rsync CLI?
Dear rsync folks,
I'd like to request/suggest that cli options to set TCP send/receive buffers
be added to rsync client-side.
Summary:
I'm aware that a daemon's config-file can set socket options for
the server side
(e.g. SO_SNDBUF, SO_RCVBUF). That is useful.
But when trying to get high-throughput rsync over
long paths (i.e. large bandwidth*delay product), since
2018 Sep 11
1
Ensuring that rsync doesn't try to write to an unmounted drive
On Tue, 2018-09-11 at 12:56 -0400, Kevin Korb via rsync wrote:
> --timeout is about network connection timeouts. You aren't using the
> network so it doesn't apply at all. Even if you were networking an
> unmounted filesystem is an empty directory as far as rsync is
> concerned
> and rsync would treat it that way with no idea that you intended to
> have
> something
2009 Jul 03
1
Bug? backup_dir sometimes reported on STDOUT, sometimes not.
Running rsync 3.0.6 on OS X 10.5.7 (on a MacBook Pro) and using the -b
flag (and -v --verbose), the "backup_dir" is reported in the output,
but sometimes on STDOUT and sometimes somewhere else. Note that the
rsync daemon running on the "server" is 2.6.9 (on another MacBook Pro,
OS X 10.5.7)
For example, in bash, this happens:
axe-MBP:bin work$ /usr/local/bin/rsync
2005 Apr 06
2
backup option
Hi,
I have question about the behavior of --backup-dir with
--delete-after option.
In my testing with version 2.6.4, it appears that the backup
option only backups altered files. Files that will be deleted on the
destination system will NOT be placed in --backup-dir location. I would
like to back up deleted files. Is there a way to do this?
Thanks