Displaying 20 results from an estimated 300 matches similar to: "increasing the write block size for high latency"
2011 Jan 09
4
DO NOT REPLY [Bug 7903] New: Cannot complete sync
https://bugzilla.samba.org/show_bug.cgi?id=7903
Summary: Cannot complete sync
Product: rsync
Version: 3.0.7
Platform: x64
OS/Version: Linux
Status: NEW
Severity: major
Priority: P3
Component: core
AssignedTo: wayned at samba.org
ReportedBy: triune at gmail.com
QAContact: rsync-qa
2008 May 18
2
rsync --files-from option file with a custom Delimiter
Hi All,
I'm new to rsync usage in Mac OS X. I'm having a strange issue with --
files-from option.
I'm providing the --files-from to provide a file , which contains the
list of files separated by newline character , to perform backup
operation. Especially in Mac OS X , particular tiff bundle files are
having \r as part of the filename.When rsync reads the filepaths using
delimiter
2015 Dec 30
10
[Bug 11656] New: Escaping broken with --files-from
https://bugzilla.samba.org/show_bug.cgi?id=11656
Bug ID: 11656
Summary: Escaping broken with --files-from
Product: rsync
Version: 3.1.1
Hardware: x64
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: core
Assignee: wayned at samba.org
Reporter:
2006 Mar 28
1
DO NOT REPLY [Bug 3637] New: Regression 2.6.6 to 2.6.7 when syncing with 2.6.6 on windows - --no-r
https://bugzilla.samba.org/show_bug.cgi?id=3637
Summary: Regression 2.6.6 to 2.6.7 when syncing with 2.6.6 on
windows - --no-r
Product: rsync
Version: 2.6.7
Platform: x86
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P3
Component: core
AssignedTo: wayned@samba.org
2002 Jun 22
0
-z and -B65536 causing file corruption in 2.5.5 w/zlib 1.1.4
When using the -z and -B65536 options together, sometimes there is file
corruption. Client and server are both compiled against zlib 1.1.4, so
the gzip corruption shouldn't be there, right?
With -z and -B32768 there is an error, but it is detected in a different
way.
With -B65536 and without -z all seems to be going OK.
With -B16384 and with -z all seems to be going OK.
I'm guessing
2003 Dec 30
2
Shorten long lines in man page options summary
One thing that's bugged me is that some of the man page lines in the
options summary are longer than 79 chars and wrap onto the next line.
These are just one line summaries (detailed description appear later)
so they can, and should, be terse.
Here's an edited diff showing my proposed changes (and a 79 char ruler):
2003 Mar 23
2
Modified --files-from patch
I've been working on an update to my --files-from patch that I think
will soon be ready to be committed to CVS. See if you agree.
For those that have been following the saga, here's a list of just the
changes since the last patch (for those that haven't, see the next
section):
Changes Since the Last Release:
===============================
- The --null option was renamed to
2004 Jan 02
0
rsync 2.6.0 (final) released
I've released version 2.6.0 of rsync. Two important things to note
in the new release:
1. The default remote shell is now "ssh" unless you tell
the configure you want to use something else.
2. Some bug fixes in the include/exclude code, while making
things work properly, have resulted in some user-visible
changes for certain wildcard strings. Read the
2003 Jan 18
2
Latest release of --files-from patch
I've worked up a new release of my --files-from patch. It has the
following changes from the last release:
New Changes:
============
- The -R option is now on by default when --files-from has been
specified. The user can specify --no-relative to turn this off.
- The -a (--archive) option does not imply -r when --files-from was
specified. The user can still specify it manually,
2005 Jan 31
1
[patch] add "--ignore" option
Hi,
The patch below adds a "--ignore" option to rsync, which means
"--exclude-but-dont-delete-even-if-we-specified--delete-excluded".
I need this for a few tasks, the simplest of which is to have rsync resist
trying to delete NetApp filers' ".snapshot" directories.
The change is fairly simple (the boolean filter returns become tri-state),
and works for me both
2015 Aug 17
7
Error with paths with ()'s
I was trying to process a bunch of folders to sync them to another drive and ran across an error I haven’t seen before. Normally I do this sync via a mounted file system, but this time I tried to do it over ssh:
find . -type f -atime -1 -exec rsync -aP {} 10.0.0.11:/Volumes/Drive5/{} \;
bash: -c: line 0: syntax error near unexpected token `('
bash: -c: line 0: `rsync --server -logDtpre.iLsfx
2004 Dec 22
2
possible bug with --files-from and --no-relative options
Skipped content of type multipart/alternative-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 925 bytes
Desc: not available
Url : http://lists.samba.org/archive/rsync/attachments/20041222/36f828dc/attachment.gif
2004 Mar 29
1
--from-files broken with remote sources
Using rsync 2.6.0 on both ends, I ran
rsync -v --files-from files andrew@pimlott.net: .
and got an error from the remote rsync. The reason is that the remote
rsync is run as
rsync --server --sender -vvR --files-from=- --from0 .
which conflicts with a check in options.c that rsync must have two
non-option arguments when --files-from is used. I tried again with the
latest nightly
2004 Aug 19
2
Syncing with --files-from
I want to sync files from remote to local. I have a file with all the
includes on the local machine.
When executing rsync with "--files-from=incfiles.txt", it fails while
trying to open "incfiles.txt" on the remote machine.
Is there a way to tell rsync to look for the file locally? Thanks, Dave.
2011 Mar 01
0
Error when filters exclude all files from transfer
Hi
I am using rsync in combination with lsyncd to do incremental backups.
The following rsync command is being executed when lsyncd detects that files have changed:
/usr/bin/rsync -lptgoDsz --filter=.\ /etc/rsync.filter -r --delete --force --from0 --files-from=- / rsynchead::school
The file /etc/rsync.filter contains the following:
+ /home/*/.kde/share/apps/kmail/mail/**
+
2014 Sep 02
1
[PATCH] rrsync: Add several long options used by BackupPC
rrsync used to throw the error
/usr/local/bin/rrsync: invalid rsync-command syntax or options
when run under BackupPC 3.2.1, with this patch full and incremental
backups work.
---
support/rrsync | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/support/rrsync b/support/rrsync
index 6f83f9d..c231ea3 100644
--- a/support/rrsync
+++ b/support/rrsync
@@ -60,6 +60,7 @@ our
2015 Aug 17
0
Error with paths with ()'s
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
If you want find to generate your list use --files-from:
find . -type f -atime -1 -print0 | rsync -aP --files-from=- --from0 .
10.0.0.11:/Volumes/Drive5/
On 08/17/2015 02:13 AM, @lbutlr wrote:
> I was trying to process a bunch of folders to sync them to another
> drive and ran across an error I haven’t seen before. Normally I do
> this sync
2006 May 24
0
rsync connection limit
Hello!
In the attached file is patch for the option to set client connection limit.
We had problem for dead hosts, so default system timeout is not enough.
--conlimit option added
Will be great to see this patch in the future version, so we do not need
to patch every time.
Thanks and Cheers, Eugene.
--
-------------- next part --------------
diff -Naur rsync-2.6.8/errcode.h
2007 Feb 03
1
Man page suggestion: organize options into sections
Dear rsync people (particularly Wayne),
I think it would be helpful for the options in the man page to be
divided into sections based on which aspect of rsync's behavior they
affect. Each section could also document rsync's default behavior
when none of the options are given. Collecting all the possibilities
for each aspect of rsync's behavior in one place would make it much
easier
2005 Apr 13
5
An idea: rsyncfs, an rsync-based real-time replicated filesystem
This is only my second email to the rsync mailing list. My first was sent
under the title "Re: TODO hardlink performance optimizations" on Jan 3,
2004. The response of the rsync developers to that email was remarkable
(in my opinion). I felt that the rsync performance enhancements that
resulted from the ensuing discussion and code improvements were so
consequential that I dared not