similar to: Idle option in rsync

Hi. Upgrading 2.6 to 3 version in rsync daemon changed the "refuse option" manner. Namely, rsyncd.conf ========= pid file = /var/run/rsyncd.pid use chroot = yes read only = yes secrets file = /etc/rsyncd.secrets [common] path = /common/ hosts allow = 10.0.0.0/16 auth users = rsync_common refuse options = e uid = 0 gid = 0 ========= $ rsync -v -a -u -z -S

Hello. What can it be, the rsyncd shows the wrong date or something is wrong with my setings? rsyncd server: # date Tue Aug 5 14:14:12 MSD 2008 rsync client: # date Tue Aug 5 14:14:45 MSD 2008 Log from a server: 2008/08/05 14:00:13 [22351] rsync on common/ from rsync_common@hostname (13.18.17.08) 2008/08/05 10:00:13 [22351] building file list 2008/08/05 10:00:14 [22351] sent 32852 bytes

Hello. Let me describe my situation. In Ukraine traffic to outside world costs much more than ukrainian trafiic, so I want to save my money and make "mirror" stream server. I set up icecast 1.3 server in USA and now I want to relay stream. Encoder connects to my ukrainian server and sends stream, and users are able to listen; now I want users to be able to connect to US mirror and

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

Fix breakage in the "hide" option support patch: - The code which initialized the global variable "dapa" was lost in commit 81c203f2, therefore EBIOS access did not work properly. Fixed by removing the global variable completely and moving all bounce buffer handling into read_sector() and write_sector(). - write_sector() copied data to the bounce buffer, but then

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

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]

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

Attempts to load *.lkrn images were failing with "Not enough memory to load specified image". These images have the su_ramdisk_max header field set to zero, and the code in core/runkernel.inc was limiting MyHighMemSize too early (before the load_high call used to load the main part of the kernel). Signed-off-by: Sergey Vlasov <vsu at altlinux.ru> --- core/runkernel.inc | 13

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

When attempting to sync multiple sources to a single area, /fs/lib# ls ./ ../ bin/ founder/ skill/ var/ I want to combine these four rsyncs /usr/local/bin/rsync --exclude '.snapshot' --stats -v --bwlimit=1024 --delete -atz 'host::lib/bin' . /usr/local/bin/rsync --exclude '.snapshot' --stats -v --bwlimit=1024 --delete -atz 'host::lib/var' .

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

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

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

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

My NFS setup is a heartbeat setup on two servers running Active/Passive DRBD. The NFS servers themselves are 1x 2 core Opterons with 8G ram and 5TB space with 16 drives and a 3ware controller. They're connected to a HP procurve switch with bonded ethernet. The sync-rates between the two DRBD nodes seem to safely reach 200Mbps or better. The processors on the active NFS servers run with a load

Oops. Missed one line in the last patch.... Roger. -- ** R.E.Wolff@BitWizard.nl ** http://www.BitWizard.nl/ ** +31-15-2600998 ** *-- BitWizard writes Linux device drivers for any device you may have! --* * The Worlds Ecosystem is a stable system. Stable systems may experience * * excursions from the stable situation. We are currently in such an * * excursion: The stable situation does

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

I'm looking at using Rsync to synchronize 600 Windows servers across the country to a central location. I'll be synchronizing about 15-20 gigs of data, but the vast majority will never change... every now and then, we would have to add new files, ranging in size from a few bytes to 1.5GB. Each server is on a slow frame relay connection and will be limited to 3KB/sec. The connections are