similar to: [Bug 7120] Variable bandwidth limit .. bwlimit

https://bugzilla.samba.org/show_bug.cgi?id=7120 Summary: Variable bandwidth limit .. bwlimit Product: rsync Version: 3.1.0 Platform: Other OS/Version: Linux Status: NEW Severity: enhancement Priority: P3 Component: core AssignedTo: wayned at samba.org ReportedBy: pmdumuid at gmail.com

Hi, this patch adds a --verbose option to FileCheck. [ An alternative name could be --debug or --debug-pattern. ] Consider a file CHECK: ... // CHECK-LABEL:bla1 // CHECK-NEXT:bla2 // CHECK-NEXT: bla3 // CHECK-NEXT:bla4 // CHECK-NEXT: bla5 ... and a FileCheck command using --verbose: ... $ echo | FileCheck CHECK --strict-whitespace --match-full-lines --verbose ... For each check the actual

Hi, this patch fixes a problem with leading/trailing whitespace matching for FileCheck --strict-whitespace --match-full-lines. Consider a text file: ... $ cat DUMP bla1 bla2 bla3 bla4 bla5 ... with some leading and trailing spaces, made more visible like this: ... $ sed 's/ /_/g' DUMP bla1 bla2 _bla3 bla4_ _bla5_ ... and a FileCheck file CHECK to match DUMP: ... $ cat CHECK //

+jyknight, who added --match-full-lines On 12/14/16 5:25 AM, Tom de Vries wrote: > Hi, > > this patch adds a --verbose option to FileCheck. [ An alternative name > could be --debug or --debug-pattern. ] > > Consider a file CHECK: > ... > // CHECK-LABEL:bla1 > // CHECK-NEXT:bla2 > // CHECK-NEXT: bla3 > // CHECK-NEXT:bla4 > // CHECK-NEXT: bla5 > ... >

Seems pretty useful! +1 to Jon's comments. Procedural remark: patches normally go to llvm-commits not llvm-dev. --paulr > -----Original Message----- > From: llvm-dev [mailto:llvm-dev-bounces at lists.llvm.org] On Behalf Of > Jonathan Roelofs via llvm-dev > Sent: Wednesday, December 14, 2016 8:09 AM > To: Tom de Vries; llvm-dev at lists.llvm.org; James Y Knight > Subject: Re:

Please send patches to llvm-commits not llvm-dev. Writing FileCheck tests has pitfalls. A test along these lines: bla0 CHECK:bla1 will actually pass, because the CHECK pattern is also part of the input so it will readily match itself. You want the CHECK lines not to match themselves, which you can easily do by introducing {{}} into the (middle of the) pattern. That is: bla0 CHECK:{{bla1}}

https://bugzilla.samba.org/show_bug.cgi?id=7120 --- Comment #7 from roland <devzero at web.de> --- please mind the note from this posting when using pv: http://superuser.com/questions/778066/using-pv1-to-limit-rsync-speed --snipp-- It seems that pv is waiting for data from rsync, and rsync is waiting for data too (stuck in select()) and not closing the input to pv. So it's a deadlock.

On 14/12/16 18:48, Robinson, Paul wrote: > Please send patches to llvm-commits not llvm-dev. > > Writing FileCheck tests has pitfalls. A test along these lines: > > bla0 > CHECK:bla1 > > will actually pass, because the CHECK pattern is also part of the input > so it will readily match itself. You want the CHECK lines not to match > themselves, which you can easily do

> -----Original Message----- > From: Tom de Vries [mailto:Tom_deVries at mentor.com] > Sent: Thursday, December 15, 2016 2:31 AM > To: Robinson, Paul > Cc: Jonathan Roelofs; llvm-dev at lists.llvm.org > Subject: Re: [llvm-dev] [FileCheck] Fix --strict-whitespace --match-full- > lines > > On 14/12/16 18:48, Robinson, Paul wrote: > > Please send patches to

Wayne replied to my original note which said that in a special situation that I was using to probe rsync to build a behavioral model that bwlimit= resulted in bimodal behavior around a 4000 kbyte/sec value. He responded with a patch that I have tested in a limited way. I have a push scenario from a local site to a remote site. I use a file that is 6.3 Megabyte in size whose checksums (when

https://bugzilla.samba.org/show_bug.cgi?id=12942 Bug ID: 12942 Summary: Traffic shaping: Make --bwlimit dynamic Product: rsync Version: 3.1.3 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 Component: core Assignee: wayned at samba.org Reporter:

Howdy, The following bug report was sent to the Debian BTS. Is there a way to have a code block immediately follow an unordered list? ----- Forwarded message from Joey Hess <joeyh at debian.org> ----- Consider this markdown: * bla * bla2 this should be treated as code block and it is not ... but if bullets are not above this, it works If the first code block is indented with

I am doing some benchmarking of rsync. I am using the --bwlimit= option to throttle down rsync to predict its operation over slow communications links. I am using rsync 2.6.2 from the release site without any patches. I downloaded the release rather than pull from the CVS tree. I have 2 servers "wilber" (the remote archive) and "judy" (the local archive) connected with a gig

I have two collection_select in my list.rhtml: <%= collection_select (:region, :id, @regionall, :id, :title,html_options={:onChange => "new Ajax.Updater(''related_provinces'',''/categories/related_provinces/" + "?id=''+this[this.selectedIndex].value, {asynchronous:true, evalScripts:true});"}) %><br> <%= render :partial =>

Hi all, I''m trying to understand why the following code doesnt work... ---------------------------------------------------------------------------------------- <html> <head> <title>blabla</title> <script type="text/javascript" src="prototype.js"></script> </head> <body> <form action="bllalba">

Hello Everyone: I've been trying to get rsync using --bwlimit using openssh for transport without success. Here's what I get: % rsync --bwlimit=20 from.com:/dir/file.txt /dest user@from.com's password: **** rsync: unrecognized option `--bwlimit=20' unexpected EOF in read_timeout I tried specifying ssh transport using both the -e option and by setting the RSYNC_RSH

# Environment (both local and remote hosts): $ /usr/bin/rsync --version rsync version 2.5.7 protocol version 26 Copyright (C) 1996-2002 by Andrew Tridgell and others <http://rsync.samba.org/> Capabilities: 64-bit files, socketpairs, hard links, symlinks, batchfiles, IPv6, 64-bit system inums, 64-bit internal inums $ uname -a Linux dbrac-01 2.4.9-e.27enterprise #1 SMP Tue

Hi list, I couldn't find anything related to this, on mailing lists or even bugzilla, so here it is. A problem with this combination exists in the new 2.6.3 where the bwlimit code got rewritten and is not present at <= 2.6.2. The problem is that on io.c:882 bwlimit_writemax is also used to control the bandwidth, but it is not initialized for the daemon mode. At options.c:772 you can see

[I'm not subscribed, please CC me on replies] Some time after 2.6.0 the --bwlimit code was enhanced, but the code now doesn't work anymore when you set the bandwidth limit for the daemon and generates error log entries like: 2005/01/13 08:17:03 [29636] rsync: writefd_unbuffered failed to write 12 \ bytes: phase "unknown" [receiver]: Success (0) 2005/01/13 08:17:03 [29636]

My impression when running with --bwlimit in combination with compression -z is that the speed to the filesystem is limited to the value given in --bwlimit. This must be contrary to the intention with --bwlimit. David