Displaying 20 results from an estimated 2000 matches similar to: "The dangers of static buffers in rsync code"
2004 Jan 25
2
scan for first existing hard-link file
Here's a patch that makes rsync try to find an existing file in a group
of hard-linked files so that it doesn't create the first one in the
group from scratch if a later file could be used instead.
Details: I decided to avoid having the code do an extra scan down the
list when we encounter the lead file in the list. This is because it
would be bad to have to do the same scan in the
2004 Feb 10
3
rsync 2.6.1cvs dumps core when preserve_hard_links and backup
I tried rsync 2.6.1cvs on my FreeBSD 4.X boxes.
It dumps core when preserve_hard_links and backup.
And SUPPORT_HARD_LINKS is true.
rsync -avH --delete --backup --backup-dir=/some/backup/dir \
srchost::dir/ dir/
The core says...
------------------------------------------------------------------------
Program terminated with signal 11, Segmentation fault.
#0 0x80536c0 in keep_backup
2004 Feb 06
4
memory reduction
As those of you who watch CVS will be aware Wayne has been
making progress in reducing memory requirements of rsync.
Much of what he has done has been the product of discussions
between he and myself that started a month ago with John Van
Essen.
Most recently Wayne has changed how the file_struct and its
associated data are allocated, eliminating the string areas.
Most of these changes have been
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
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
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.
2002 Jan 13
1
rsynd-2.5.1 / hlink.c patches
Platform: Compaq OpenVMS Alpha 7.3
Compiler: Compaq C T6.5
The following patch resolves compile problems with the HLINK.C module.
The cast on function argument for the qsort() routine was wrong, and not
allowing the compile to complete.
When the function definiton of the hlink_compare() is corrected to have
the const qualifiers, the cast inside the qsort() function call is no
longer
2004 Mar 10
4
HFS+ resource forks: WIP patch included
As you all know, rsync doesn't have any special handling
for Mac OS X HFS+ resource forks. Kevin Boyd made RsyncX
and rsync_hfs, to address this gap, but they only work when
the destination filesystem is also HFS+. I haven't been
able to find any references to an rsync that is capable of
syncing from HFS+ to UFS (etc). The only solutions I've
seen involve lots of preprocessing
2003 Oct 01
1
PATCH: option to ignore case in filenames
I have two DOS filesystems mounted on Linux as "vfat" which I want to rsync.
(They are on flash cards, so that they are also small). rsync gets tricked
because the filesystem treats names differing in only case as the same.
Thus, when it tries to sync "FOO123" with "foO123", it copies over the
"new" file, and then renames it over the old one (which it
2008 Feb 02
2
hardlinks not working with inode number > 2^31
I've been using 3.0.0pre8 to move a Debian archive from one filesystem
to another. This archive contains a daily snapshot of the Debian ftp
site, with common files hardlinked to save space.
I noticed that it was using far more space than necessary. Upon
investigation it seems that all the source files that have inode numbers
greater than 2^31 aren't being hardlinked together at the
2003 Mar 12
1
patch: typo's and gcc warnings
Two patches:
one to correct the spelling of permissions (in comments, but such typos
disturb me as well), and
one to cast inode and dev to unsigned long before comparing, to prevent
gcc giving a warning "comparison between signed and unsigned".
Paul Slootman
-------------- next part --------------
diff -ru orig/rsync-2.5.6/generator.c rsync-2.5.6/generator.c
---
2018 Dec 30
2
--partial does not "unhide" the files
Hi,
I used --partial to transfer files from my local computer (rsync 3.1.2,
Debian) to a remote computer (rsync 3.1.1 WD MyPassport Storage device)
The files get transferred, but after successful transfer, the files
are not renamed from .<tmpfile> to <file>.
Where to go next?
Here is the verbose output after transferring an empty file
heiko at blade:~/Pictures$ rsync
2003 Sep 05
1
new option suggestion '--backup-only'
Hi,
How about adding now option '--backup-only' that means making backups
only and don't change any destination files?
(I posted similar patch a month ago, but the patch was made for
nightly snapshot of 20020808, which was tooo old! Laugh at me...)
I want to use rsync with LVM snapshot to make incremental backups like
below:
1) Make LVM snapshot of file system and mount it.
2003 Jan 14
3
.rsync-/.rsync+ patch and --link-dest example
This is a patch to add an --rsync-exclude option to rsync-2.5.6cvs.
File names in .rsync- (or .rsync+) are excluded (or included) from the file
lists associated with the current directory and all of its subdirectories.
This has advantages over --cvs-exclude for backing up large file systems
since the .cvsignore files only apply to the current directory:
unless the .cvsignore restrictions apply
2002 May 04
1
A simpler move-files patch
In an effort to get my long-desired move-files functionality into rsync,
I have created a version of my patch that runs as an extra pass at the
end of the processing. This results in a simpler set of changes to
rsync.
I still think it would be nice to have incremental deletions during
large transfers (as my first patch provides), but acceptance of this
patch would relegate such quibbling to a
2003 Oct 18
0
Added functionality --compare-file and --compare-auto
Recently various needs for multiple version handling were discussed
and I put forward a plan of mine. Subsequently the proposal for a
--compare-file=<FILE> switch had support, so I have implemented
this. I have also implemented an experimental --compare-auto which
decides which file to match against using a rule.
Instructions for patch:
1. Install rsync-2.5.6 source
2. "patch -p1
2004 Apr 10
0
patches for copying atimes
Hi.
Here's a patch for copying the atimes of files when -t/--times is
given. I bumped the protocol to 29 since it sends more data over the
wire. It obviously does not send the atime if it's sending data to an
older rsync version.
It passes all the tests (including the added atime.test) for me on a:
Linux Debian/3.0 gcc 2.95.4 (debian), glibc 2.2.5 system.
Any questions/feedback? I
2002 Feb 19
1
rsync bug in clean_flist() while removing duplicted names
hello,
i use rsync as a major backend for our automatic debian GNU/linux
workstation synchronisation project at the Free University of Berlin /
Computer Science.
my concept is, that rsync gets the class, group and machine-specific
root-trees as argument, and it's up to him to find and automaticaly
remove duplicated files on the basis of the priority (which is actually
the argument list).
2003 Mar 30
1
[RFC][patch] dynamic rolling block and sum sizes II
Mark II of the patch set.
The first patch (dynsumlen2.patch) increments the protocol
version to support per-file dynamic block checksum sizes.
It is a prerequisite for varsumlen2.patch.
varsumlen2.patch implements per-file dynamic block and checksum
sizes.
The current block size calculation only applies to files
between 7MB and 160MB setting the block size to 1/10,0000 of
the file length for a
2011 Dec 16
5
[Bug 8666] New: --debug=all9 fail
https://bugzilla.samba.org/show_bug.cgi?id=8666
Summary: --debug=all9 fail
Product: rsync
Version: 3.1.0
Platform: All
OS/Version: All
Status: NEW
Severity: normal
Priority: P5
Component: core
AssignedTo: wayned at samba.org
ReportedBy: chris at onthe.net.au
QAContact: rsync-qa at