similar to: RSYNC_ARG# question

Displaying 20 results from an estimated 30000 matches similar to: "RSYNC_ARG# question"

2006 Aug 06
2
File fragmentation
I've been running some tests on files created by rsync and noticing fragmentation issues. I started the testing because our 5TB array started performing very slowly and it appears fragmentation was the culprit. The test I conducted was straighforward: 1. Copy over a 49GB file. Analyzed with contig (from sysinternals), no fragments. 2. Ran rsync and the file was recreated normally (rsync
2006 Sep 20
1
Clarification on the RSYNC_EXIT_STATUS
I'm guessing no one else has seen this issue? Most exit codes are properly reported (e.g. code 12, code 10, code 2). The specific scenario is when a filename too long or directory not present error causes the client to exit with a code of 23 (reported as the exit code on the client properly and captured in the environment variable there). The exit code of the server still shows an exit code
2006 Mar 13
2
feature request/change for 2.6.8
Wayne, I've been experimenting with the {pre,post}-xfer exec options ever since the original diff showed up in patches/ - fantastic stuff. My feature request/change centers around the new RSYNC_ARG# variables. Would it be possible to make these available as an array (ie: ${RSYNC_ARG[#]}) rather than discrete variables? If nothing else, it would greatly simplify chewing through all the args
2007 Nov 05
13
preallocate CPU usage - pre4
When I use the preallocate patch and create a 77GB file using the function I get a CPU spike on the server-side. The spike lasts about 20 minutes and uses about 20%-25% of the cpu associated with the rsync instance creating the file. The spike is directly linked to the time it takes to create the file. I compiled rsync using cygwin CVS. I initially suspected the implementation of
2006 Sep 18
2
Clarification on the RSYNC_RAW_STATUS and RSYNC_EXIT_STATUS
I've noticed that even if rsync has a non-zero exit code on the client that the server still reports an exit status of 0. For example, I've received an error 23 with the following output on the client-side "rsync error: some files could not be transferred (code 23) at main.c(954) [sender=2.6.9cvs]" while the server-side rsync_raw_status and rsync_exit_status were still both
2008 Feb 03
5
Compiling with --disable-iconv
I've been trying to compile 3.0.0pre8 under cygwin. I was getting a problem with the iconv functions which I think are related to the cygwin environment and its iconv.h. To bypass it I wanted to compile with the --disable-iconv function. I'm still getting the following errors during compile: /usr/src/rsync-3.0.0pre8/rsync.c:85: undefined reference to `_iconv_open'rsync.o: In
2006 Sep 13
2
File fragmentation
Wayne.my vote is for a command-line option. I've noticed there is some penalty for very large files (35GB-50GB). The penalty is relatively small based on my 'intuitive' measurements.read me watching without running a real timer. The difference is very small compared to what happens after a few weeks without the fragmentation patch. Our SAN was becoming so fragmented that we were
2017 Apr 21
0
[PATCH 1/2] generator: Simplify the handling of string parameters.
Previously we had lots of types like String, Device, StringList, DeviceList, etc. where Device was just a String with magical properties (but only inside the daemon), and DeviceList was just a list of Device strings. Replace these with some simple top-level types: String StringList and move the magic into a subtype. The change is mechanical, for example: old
2008 Jan 30
2
--partial replaces destination file on interrupted transfer
I had a case where I was using the --partial option (client is running rsync-pre5, server daemon is rsync-pre8). The transfer was interrupted and the partially transferred file replaced the destination file on the server. My understanding is that the partially transferred file would be kept but it would not replace the destination file...that is, both files would be kept so that rsync could pick
2002 Feb 22
1
Head & Rotor VE(CHINA-LuTong) 2/23
Dear Sir, My name is ChenHua, and I'm writing on behalf of the China-Lutong mechanical company. Located in the south east of China, we specialize in hydraulic heads for the VE distributor pump. We can supply standard, good quality units at a very competitive price. The following types are available: Engine model VE PUMS code NO UNIT PRICE(EX WORKS) ISUZU) NP-VE4/11L
2004 Aug 06
1
Head & Rotor VE(CHINA-LuTong) 2/23
Dear Sir, My name is ChenHua, and I'm writing on behalf of the China-Lutong mechanical company. Located in the south east of China, we specialize in hydraulic heads for the VE distributor pump. We can supply standard, good quality units at a very competitive price. The following types are available: Engine model VE PUMS code NO UNIT PRICE(EX WORKS) ISUZU) NP-VE4/11L
2002 Feb 26
1
Head & Rotor VE(CHINA-LuTong) 2/23
Dear Sir, My name is ChenHua, and I'm writing on behalf of the China-Lutong mechanical company. Located in the south east of China, we specialize in hydraulic heads for the VE distributor pump. We can supply standard, good quality units at a very competitive price. The following types are available: Engine model VE PUMS code NO UNIT PRICE(EX WORKS) ISUZU) NP-VE4/11L
2008 Sep 30
1
Question on "Resource temporarily unavailable" error
I'm using rsync over an ssh tunnel to transfer some large files. I've been getting the "Resource temporarily unavailable" in my rsyncd.log frequently. The connections are T1's and very stable so I don't think it is a network drop. The disconnect occurs on the same files every time...although these files are also the largest ones taking the most time. I tried limiting
2008 Feb 27
2
Unix-like touch to update modification timestamp of file?
Hi, is it possible to update the modification time stamp of a file using R (on file systems supporting it)? It is sufficient to update the modification time to the current time. The best I can do for now is: touchFile <- function(pathname, ...) { if (!file.exists(pathname)) stop("No such file: ", pathname); info <- file.info(pathname); if (info$isdir)
2015 Oct 20
0
[PATCH 2/2] actions: turn some params into RelativePathnameList (RHBZ#1174551).
Use RelativePathnameList as type for lists of relative paths, as used in some listing-alike APIs. This way we can ensure absolute paths in those lists are rejects outright. As a consequence, test-big-dirs.pl does not need to prepend the directory name anymore before calling listing-alike APIs: previously they didn't fail, but the returned lists contained only invalid elements (and only their
2007 Mar 31
1
Too long pathname in bitmap() crashes R on WinXP
Hi, using too long pathnames for bitmap() crash R on WinXP. I've verified that this is the case with R version 2.4.1 Patched (2007-03-25 r40958) and R version 2.5.0 alpha (2007-03-30 r40957). I cannot reproduce it on Linux. REPRODUCIBLE EXAMPLE: % Rterm --vanilla # Tell R where Ghostscript is gsexe <- "C:/gs/gs8.54/bin/gswin32c.exe"; gsexe <- "C:/Program
2012 Jan 16
1
[PATCH] generator: Add an explicit Cancellable flag
Currently any api which takes a FileIn or FileOut parameter is implicitly cancellable. This change make cancellable an explicit flag in anticipation of it being added to other apis. --- generator/generator_actions.ml | 53 ++++++++++++++++++++++++++------------- generator/generator_checks.ml | 3 +- generator/generator_types.ml | 1 + 3 files changed, 38 insertions(+), 19 deletions(-)
2003 Mar 04
1
2.5.6 needs following fix on WinNTs
Hi, Here is the problem (syscall.c, function do_open) on NT, Win2K, WinXP, with stripped "/" for UNC path convention, detected in release 2.5.5, 2.5.6: int do_open(char *pathname, int flags, mode_t mode) { if (flags != O_RDONLY) { if (dry_run) return -1; CHECK_RO } #ifdef O_BINARY /* for Windows */ flags |= O_BINARY; #endif /* some systems can't handle a double / */
2016 Jul 25
2
[PATCH] osinfo: revamp db reading (RHBZ#1359652)
More recent versions of libosinfo switched the internal directory with the XML files of OSes to a different layout (still with the same XML format), causing libguestfs to not read them anymore. Furthermore, the internal directory is going to disappear soon, replaced by a public osinfo database [1]. Revamp the way libguestfs reads the data: first try the upcoming osinfo layout, falling back to
2013 Feb 07
12
[PATCH 01/12] generator: Add new Mountable argument type
This type is initially identical to Device. --- generator/bindtests.ml | 2 +- generator/c.ml | 7 +++++-- generator/csharp.ml | 6 ++++-- generator/daemon.ml | 4 ++-- generator/erlang.ml | 6 +++--- generator/fish.ml | 8 ++++---- generator/gobject.ml | 11 ++++++----- generator/haskell.ml | 11 +++++++---- generator/java.ml | 10 +++++-----