Displaying 20 results from an estimated 30000 matches similar to: "[Bug 2104] Implement --only-write-batch=FILE"
2004 Nov 30
0
[Bug 2104] New: Add support for --dry-run with --write-batch
https://bugzilla.samba.org/show_bug.cgi?id=2104
Summary: Add support for --dry-run with --write-batch
Product: rsync
Version: 2.6.3
Platform: All
OS/Version: All
Status: NEW
Severity: enhancement
Priority: P3
Component: core
AssignedTo: wayned@samba.org
ReportedBy: wayned@samba.org
2005 Feb 12
0
[Bug 2104] Add support for --dry-run with --write-batch
https://bugzilla.samba.org/show_bug.cgi?id=2104
wayned@samba.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
------- Additional Comments From wayned@samba.org 2005-02-12 15:01 -------
This should not be that hard. The generator would
2005 Mar 28
2
"batched dry-run"... sort of
I'd like to know if it's possible to run rsync in batch mode, but avoiding
transferring the deltas, just generating the batch file.
I'm looking for such a behaviour because overnight backup sessions are
often interrupted and daily snapshots (--link-dest) of remote servers are
truncated. Specially the ones using slow links.
Options:
1) Using -write-batch when mirroring volume
2005 Mar 29
1
Rsync 2.6.4pre4 released (2.6.4 imminent!)
I've released rsync 2.6.4pre4. I believe that this version will be what
gets released as 2.6.4, hopefully on Wednesday. Please try this out
and let me know if anything is amiss.
All the changes since 2.6.3 are mentioned here:
http://rsync.samba.org/ftp/rsync/preview/NEWS
You'll also find a preview of the man pages in the same dir (as usual):
2005 Mar 29
1
Rsync 2.6.4pre4 released (2.6.4 imminent!)
I've released rsync 2.6.4pre4. I believe that this version will be what
gets released as 2.6.4, hopefully on Wednesday. Please try this out
and let me know if anything is amiss.
All the changes since 2.6.3 are mentioned here:
http://rsync.samba.org/ftp/rsync/preview/NEWS
You'll also find a preview of the man pages in the same dir (as usual):
2011 Nov 02
2
[Bug 8565] New: rsync hangs when using --only-write-batch and --hard-links
https://bugzilla.samba.org/show_bug.cgi?id=8565
Summary: rsync hangs when using --only-write-batch and
--hard-links
Product: rsync
Version: 3.1.0
Platform: x64
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P5
Component: core
AssignedTo: wayned at samba.org
2008 Feb 16
1
DO NOT REPLY [Bug 5265] New: Daemon logging files not actually received with --only-write-batch
https://bugzilla.samba.org/show_bug.cgi?id=5265
Summary: Daemon logging files not actually received with --only-
write-batch
Product: rsync
Version: 3.0.0
Platform: Other
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P3
Component: core
AssignedTo: wayned@samba.org
2007 Nov 11
1
DO NOT REPLY [Bug 5074] New: Push to a daemon with --only-write-batch modifies dest and then hangs
https://bugzilla.samba.org/show_bug.cgi?id=5074
Summary: Push to a daemon with --only-write-batch modifies dest
and then hangs
Product: rsync
Version: 3.0.0
Platform: x86
OS/Version: Linux
Status: NEW
Severity: major
Priority: P3
Component: core
AssignedTo: wayned@samba.org
2012 Mar 09
1
[Bug 8804] New: rsync -aH --only-write-batch hangs
https://bugzilla.samba.org/show_bug.cgi?id=8804
Summary: rsync -aH --only-write-batch hangs
Product: rsync
Version: 3.0.9
Platform: x64
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P5
Component: core
AssignedTo: wayned at samba.org
ReportedBy: christian.heinlein at htw-aalen.de
2007 Jul 14
1
DO NOT REPLY [Bug 4786] New: deletes files in parent directory when destination directory doesn't exist
https://bugzilla.samba.org/show_bug.cgi?id=4786
Summary: deletes files in parent directory when destination
directory doesn't exist
Product: rsync
Version: 2.6.9
Platform: Other
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P3
Component: core
AssignedTo:
2004 Nov 25
1
Feature suggestion: --write-batch --dry-run
AFAICS, --write-batch logs the changes made while doing an rsync
operation from place A to place B, and lets you then use the batch file
to apply those changes to place C if it were hitherto the same as B. I
reckon it'd be a good feature to have a mode where the changes can be
logged *without* updating B, so that the update to B itself can be done
from the batch file.
The motivation for this
2008 Jan 14
7
DO NOT REPLY [Bug 5201] New: Rsync lets user corrupt dest by applying non-inplace batch in inplace mode
https://bugzilla.samba.org/show_bug.cgi?id=5201
Summary: Rsync lets user corrupt dest by applying non-inplace
batch in inplace mode
Product: rsync
Version: 3.0.0
Platform: Other
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P3
Component: core
AssignedTo:
2007 Dec 11
2
"yum --security" and staying with 5.0
Hello,
So I've watched a few threads about the new 5.0 vs. 5.1 upgrade and
have a couple of (hopefully) practical questions about this:
Context - I'd like to stick to 5.0 at least for a while until the dust
around 5.1 settles down (and I'm back from holidays).
As an example - In Debian, as long as I stick to "stable" I can be
sure that the only updates I receive there are
2013 Nov 06
0
[LLVMdev] [cfe-dev] RFC: A proposal to move toward using C++11 features in LLVM & Clang / bounding support for old host compilers
>> If the new feature requires out-of-tree LLVM users to upgrade their
>> toolchains then we may only be giving them a month or less warning,
>> even if we are giving downstream packagers 6 months.
>
> Correct. That's not enough warning.
If we decide to delay this yet again (it's been on the cards since
January, so I'm personally opposed, but still...) we
2006 Jan 18
7
DO NOT REPLY [Bug 3422] New: dry run fails when encountering dangling symbolic link
https://bugzilla.samba.org/show_bug.cgi?id=3422
Summary: dry run fails when encountering dangling symbolic link
Product: rsync
Version: 2.6.4
Platform: All
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P3
Component: core
AssignedTo: wayned@samba.org
ReportedBy:
2013 Nov 21
0
--remove-source-files problem when used with --write-batch
I used this rsync command:
rsync -az --only-write-batch=tmp.rsync --inplace --remove-source-files --include='*' --include='*/' tmp/ nonexistent_dir
which created file tmp.rsync.sh containing this rsync command:
rsync --filter=._- -az --read-batch=tmp.rsync --inplace --remove-source-files ${1:-nonexistent_dir} <<'#E#
which when executed gives the error:
2004 Jun 21
2
problems with --read-batch and --write-batch with --files-from
Hello,
I want to use the --read/write-batch options, but i have problems to do so.
The shell script [1] leads to the following error:
[sender] expand file_list to 131072 bytes, did move
delta-transmission disabled for local transfer or --whole-file
file1
rsync: writefd_unbuffered failed to write 64 bytes: phase "unknown":
Daten?bergabe unterbrochen (broken pipe)
rsync error: error in
2013 May 15
3
[Bug 2104] New: Windows/win32/mingw support
https://bugzilla.mindrot.org/show_bug.cgi?id=2104
Bug ID: 2104
Summary: Windows/win32/mingw support
Classification: Unclassified
Product: Portable OpenSSH
Version: -current
Hardware: Other
OS: Linux
Status: NEW
Severity: enhancement
Priority: P5
Component: Miscellaneous
2004 Apr 30
1
--write-batch just hangs?
I'm using rsync version 2.5.7, and I see this behavior with Debian and Redhat installations.
This works:
rsync rsync://mirror.physics.ncsu.edu/redhat/linux/updates/9/en/os/i386/zebra* ./temp
But this doesn't:
rsync --write-batch=mytest rsync://mirror.physics.ncsu.edu/redhat/linux/updates/9/en/os/i386/zebra* ./temp
I've also tried with my normal args, like "-vvvvv --progress -t
2007 Mar 13
1
Feature-Request: --write-batch on destination not source
Hi
I have a "Chain" of rsyncs(*)
A -> B -> C -> D
My problem is that "A" is switched off after the rsync is done. So i
have to copy the "batch" immediately (and manually/via other means) to
"B", before switching off, so the batch can later be retrieved from "B"
and copied to "C" for --read-batch. And copied further on for