similar to: DO NOT REPLY [Bug 6881] New: --bwlimit option uses KiB/s, but is documented as (what amounts to) kB/s

I'm getting lots of errors like this (possibly on every message delivery): imap2 dovecot: lmtp(rlaager at wiktel.com): Error: OU02K+gQmFhUAwAAVtfydQ : sieve: binary save: failed to create temporary file: open(/var/lib/dovecot/sieve/junk-mail.svbin.ima p2.852.) failed: Permission denied (euid=500(vmail) egid=500(vmail) missing +w perm: /var/lib/dovecot/ sieve, dir owned by 0:0 mode=0755)

On 03/04/2016 08:52 AM, Timo Sirainen wrote: > On 04 Mar 2016, at 07:47, Richard Laager <rlaager at wiktel.com> wrote: >> Is there any way to disable the header hashing in dsync? ... > Does the attached patch happen to work? Compiles, but untested for now. It works with one more change on top of your patch: diff --git a/src/doveadm/dsync/dsync-mailbox-export.c

Is there any way to disable the header hashing in dsync? I'm doing a one-time migration to Dovecot using imapc. The FETCHes for Date & Message-ID take a non-trivial amount of time and it's not clear to me if they have a function for a one-time migration. -- Richard

Hi, I am currently working on a managesieve daemon, so that I can use the squirrelmail plugin avelsieve together with dovecot-lda. Without this I can't migrate from cyrus to dovecot. For several reasons I don't use the timsieved from cyrus and build it from scratch. Is this interesting for somebody else? Gerald

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

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

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

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]

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

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

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

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

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

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

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

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

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

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

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