similar to: [Bug 12942] New: Traffic shaping: Make --bwlimit dynamic

Displaying 20 results from an estimated 1000 matches similar to: "[Bug 12942] New: Traffic shaping: Make --bwlimit dynamic"

2010 Feb 09
9
DO NOT REPLY [Bug 7120] New: 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
2017 Mar 01
0
[Bug 7120] Variable bandwidth limit .. bwlimit
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.
2002 Jan 04
1
rsync -e ssh --bwlimit=20 ?
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
2013 Mar 06
1
[Bug 7120] Variable bandwidth limit .. bwlimit
mhh - interesting question...... what about combining the power of throttle ( http://linux.die.net/man/1/throttle ) or similar tools (there are some more like this) with rsync ? via this hint: http://lists.samba.org/archive/rsync/2006-February/014623.html i got a clue how to combine rsync and throttle and gave it a try : cat throttle-wrap #!/bin/bash throttle -k 1 -s 1| "$@" rsync
2004 May 25
0
--bwlimit - writing vs reading performance
# 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
2004 May 21
2
question about --bwlimit=
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
2003 Jun 18
0
bwlimit patch.
Hi, I Emailed this afternoon that bwlimit leads to a much too low bwlimit if small amounts of data are sent in each write. I wrote a small patch now. Congrats on the code: It's nice and clean: I wrote a working patch in 5 minutes after examining a total of 25 lines of code. (My backup used to require two hours of small sleeps alone, which should be reduced by a factor of 8....)
2005 Jun 14
0
[Bug 2800] New: bwlimit effects checksum speed
https://bugzilla.samba.org/show_bug.cgi?id=2800 Summary: bwlimit effects checksum speed Product: rsync Version: 2.6.0 Platform: All OS/Version: All Status: NEW Severity: minor Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: schwern@pobox.com QAContact:
2004 Nov 04
1
Problems with --bwlimit && --daemon
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
2005 Jan 13
1
--bwlimit doesn't work for daemon mode
[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]
2008 Mar 28
1
bwlimit on rsync locally
Does "bwlimit" option really work on rsync locally? We have one type of harddisk and want to slow down rsync I/O on disk because I don't want the disk head gets too hot. While I'm trying to use --bwlimit option, it looks the rsync speed was slowed down, but iostat is not improved at all. In both case the block written speed is increased by the same amount. How could I really
2013 Feb 13
2
[Bug 9660] New: rsync --daemon --bwlimit does not work on server side
https://bugzilla.samba.org/show_bug.cgi?id=9660 Summary: rsync --daemon --bwlimit does not work on server side Product: rsync Version: 3.0.9 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: mopp at gmx.net
2004 May 26
1
bwlimit=
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
2003 Apr 15
1
Two --bwlimit issues
Hi, I have two issues with the --bwlimit parameter to rsync which are not mentioned in the FAQ (please correct me if I am wrong): 1. When both an rsync client and an rsync daemon specify the --bwlimit parameter, the client's value overrides the server's value. This could be used in a DOS attack if the client uses a larger value than the server intended. The documentation also is
2003 Oct 17
2
--bwlimit not working right
Hello! I cant get the bwlimit option working right. If i set this option over 400 kbyte per sec i still only get 400kbyte per sec, whether wich value i set. I try this option with a 100MB big file. I use a debian stable System with rsync version 2.5.6cvs protocol version 26. Can someone tell me how i can this get working? thx Rene dpkg -l "rsync*" ii rsync 2.5.5-0.1 fast remote
2007 Feb 16
3
--bwlimit -z limits filesystem speed, not network speed
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
2011 Jan 21
2
Issue with bwlimit after resuming a partial transfer due to a communication break
I am using rsync version 3.0.7. My rsync server is running on the cloud. I have set the bwlimit to 10 i.e. 10 KBps. When I try to sync files the bwlimit is as what is set. I have enabled storage of partial files. When a communication break causes rsync to time out during a transfer the partial file is stored in the partial directory. I then try rsync again when the link is up. At this point I see
2010 Jul 29
1
Add bwlimit to SSH Single Use Deamon
Hello List. is there any way to add an bwlimit to an SSH Singel USe Deamon? My cutomer want to use ssh and i want to set an Bandwith limit. As long that bwlimit is not an rsyncd.conf option i see no way to add ist for ssh connections. I am using debian Lenny with rsync 3.0.3 Thnaks, Mark -- Mark Eisenbl?tter Gei?end?rfer & Leschinsky GmbH www.gl-systemhaus.de -------------- next part
2012 Sep 28
1
dynamic bwlimit with rsync
Hi, Is there a way to do rsync with varying bwlimit during the transfer. I tried to look using Linux 'tc' but it looks trivial. Do somebody has working model for it? Our pipe is limited and we don't want to give everything to rsync, We have situation where we want rsync transfers to scale up or down within a specified bandwidth limit. For e.g. if there are two (or multiple) rsyncs
2004 Nov 17
1
specifying --bwlimit together with --daemon fails
I received a bug report that starting with 2.6.3, rsync fails when started from inetd with the --bwlimit option (actually, I narrowed it down to that :-). Earlier rsync versions did work. What I see from the strace output is that the rsync --daemon process sets fd 0 to ON_NONBLOCK, then does a select() on fd 0 for write (which shows it's ready for writing), and then does a write of zero