similar to: Two --bwlimit issues

Hello, For an internal project we were looking for a solution which extends ActiveRecord by an iterator function. Using find(:all) is no fun if you have to process some 10.000 records. Until now there have been two ways of dealing with that scenario: - write your logic a second times (e.g. use stored procedure) - bet on AR plugins which work around that limitation by fetching IDs and

https://bugzilla.samba.org/show_bug.cgi?id=2654 wayned@samba.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED ------- Additional Comments From wayned@samba.org 2005-04-27 02:21 ------- The generator's setting of the ignore_timeout

I have released rsync 2.6.4pre1 -- the first preview release of 2.6.4. Please try it out and send feedback to the mailing-list or directly to me, as appropriate. For a list of what has changed since 2.6.3, see the NEWS file: http://rsync.samba.org/ftp/rsync/preview/rsync-2.6.4pre1-NEWS For the tar file itself, you'll find it here (with its signature):

I have released rsync 2.6.4pre1 -- the first preview release of 2.6.4. Please try it out and send feedback to the mailing-list or directly to me, as appropriate. For a list of what has changed since 2.6.3, see the NEWS file: http://rsync.samba.org/ftp/rsync/preview/rsync-2.6.4pre1-NEWS For the tar file itself, you'll find it here (with its signature):

Hello rsync-users, I need to transfer an PC image-file (200 to 400 MB) to 500 locations, which are equal as concurrent users on the day X. what parameters do you suggest to use on the central rsync-server? any recommendation for socket options? is it a good idea to split the file into several pieces, let?s say 10 MB ? Does this speed up the blocksum calculation or is it better to leave the

is it possible and how difficult is it, to use LDAP for all the user accounts and groups and password management? would this be something you would want to do? or is it better to stick with samba's initila way of dealing with users? Caleb O'Connell caleb@lincoln.midcoast.com (207)882-7792

We are using rsync to backup files from a bunch of computers to a central server using rsync in --daemon mode. I've got a problem and are looking for suggestions. I'm not a newbie to rsync and have checked the archives without getting any useable conclusions. Our old server works great - a redhat 7.2 / 2.4.18 machine. But it's getting full and there's no more updates for

I want to use rsync under the control (ie. initiated from) the client side, but with the bandwidth controlled by the server side. I can force the bwlimit option on the command line executed on the server, but will this make a difference given that the files are being sent from client to server? If not, is there some other way to limit this bandwidth inbound to the server? I know that I can

Is there any plan to do it? Is it maybe already in and just not documented? -- Lapo 'Raist' Luchini lapo@lapo.it (PGP & X.509 keys available) http://www.lapo.it (ICQ UIN: 529796)

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

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

u_int64_t has been introduced into scp.c with the new bwlimit function causing some platforms to break. Would this work? ----------------------------------- --- scp.c.old 2003-03-09 17:16:43.000000000 -0800 +++ scp.c 2003-03-16 16:17:57.095520029 -0800 @@ -670,7 +670,7 @@ { static struct timeval bwstart, bwend; static int lamt, thresh = 16384; - u_int64_t wait; + off_t wait; struct

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....)

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 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

[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]

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:

Hi, Any one give me some sample code with bwlimit option. what's is the std/ recommended value for this?

I am using rsync in a situation where the amount of bwlimit I want to use changes depending on the time of day. for example, I start rsync at 2am when no-one else is using the system, so I want it to use 100k/sec. At 9am, it is still running, but as the bandwidth of the link it's using now needs to be shared with other users, I would like rsync to only use 10k/sec. Any way of doing this

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