similar to: rsync --daemon only binding against IPv6

On Wed, Jan 30, 2002 at 06:03:10PM -0500, Bill Nottingham wrote: > Dave Dykstra (dwd@bell-labs.com) said: > > I stumbled across the bug report > > http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=58878 > > > > which shows that you made a bug fix to rsync on Sunday. What exactly did > > you do? > > Attached. It's the same thing as yours, I just

On Wed, Dec 10, 2014 at 09:26:31PM +0100, Reindl Harald wrote: > > Am 10.12.2014 um 21:19 schrieb Thomas Klausner: > >I have lots of these files: > > > >/home/wiz/Mail/my-folder-name/cur/.imap/1238738125.13533_23713.danbala:2,S/dovecot.index.log > > > >What are they for? > >Why are they here? > >Can I remove them? > > RTFM:

I recently became the new rsync maintainer for Red Hat, and I just completed a review of the current patches that we (Red Hat) maintain for 'rsync'. After removing three unnecessary patches (either already incorporated into rsync-2.5.6, or were outdated and couldn't be applied), we are left with one patch - rsync-2.5.6-sign.patch - which I have attached.

Greetings, I'd like to propose a new option to rsync, which causes it to read device files as if they were regular files. This includes pipes, character devices and block devices (I'm not sure about sockets). The main motivation is cases where you need to synchronize a large amount of data that is not available as regular files, as in the following scenarios: * Keep a copy of a block

Currently rsync has a bit of a problem with very large files. Dynamic block sizes were introduced to try handle that automatically if the user didn't specify a block size. Unfortunately that isn't enough and the block size would need to grow faster than the file. Besides, overly large block sizes mean large amounts of data need to be copied even for small changes. The maths indicate

Am 10.12.2014 um 21:19 schrieb Thomas Klausner: > I have lots of these files: > > /home/wiz/Mail/my-folder-name/cur/.imap/1238738125.13533_23713.danbala:2,S/dovecot.index.log > > What are they for? > Why are they here? > Can I remove them? RTFM: http://wiki2.dovecot.org/IndexFiles https://www.google.at/search?q=dovecot.index.log -------------- next part -------------- A

Hi! I have lots of these files: /home/wiz/Mail/my-folder-name/cur/.imap/1238738125.13533_23713.danbala:2,S/dovecot.index.log What are they for? Why are they here? Can I remove them? Thomas

Mark II of the patch set. The first patch (dynsumlen2.patch) increments the protocol version to support per-file dynamic block checksum sizes. It is a prerequisite for varsumlen2.patch. varsumlen2.patch implements per-file dynamic block and checksum sizes. The current block size calculation only applies to files between 7MB and 160MB setting the block size to 1/10,0000 of the file length for a

Attached is a patch that makes window strides constant when files are walked with a constant block size. In these cases, it completely avoids all memmoves. In my simple local test of rsyncing 57MB of 10 local files, memmoved bytes went from 18MB to zero. I haven't tested this for a big variety of file cases. I think that this will always reduce the memmoves involved with walking a large

--- Erhalten von ZBM.ZARBR 089/32000-545 24-02-03 12.07 Hi, I mirror a server installation using rsync 2.5.6 (on both sides) with these options: -a -x --numeric-ids -H --delete --stats -e ssh -z --exclude-from ... This happens every night. In about 80% of the cases rsync returns exit status 12 when trying to transfer a certain file. In the other 20% the file is

Hi Folks, Similar to an earlier thread, but slightly more ordinary. My old rsync backup script, which worked fine under Ubuntu 12.04, hangs on Ubuntu 12.10 (rsync 3.0.9) and a 250 MB file. Command line as follows: rsync --itemize-changes --human-readable --progress --delete \ --delete-excluded --compress --bwlimit=18 --recursive --archive \ --partial --partial-dir=~/partial

OK. I got the rsync CVS code and compiled under Linux. That did the job, but only with --no-whole-file because of the local transfer. I then tried to read-batch... under Windows / Cygwin with the current Cygwin rsync. That didn't work - as expected. After compiling again under cygwin it worked! I can now create a diff from a new CD to the version before and send the diff files by email. On

After fresh installation of CentOS 6.2 on my server, I get following errors in my dmesg output: ------- MTRR default type: uncachable MTRR fixed ranges enabled: 00000-9FFFF write-back A0000-BFFFF uncachable C0000-D7FFF write-protect D8000-E7FFF uncachable E8000-FFFFF write-protect MTRR variable ranges enabled: 0 base 000000000 mask C00000000 write-back 1 base 400000000 mask

Good Day All, Today I looked at the dmesg log and I notice that the following messages regarding mtrr_gran_size/mtrr_chunk_size. I am currently running CentOS 6.3 and I installed CentOS 6.2 and 6.1 and I was seeing the same errors. When I installed CentOS 5.8 on the same laptop I do not see these errors. $ lsb_release -a LSB Version:

Hi, I have server that has been running 5.x - 5.8 for a few years without issue and decided to move it to a fresh install of 6.2. First thing I noticed is a good part of the log has these mtrr messages finally ending with "mtrr_cleanup: can not find optimal value" and "please specify mtrr_gran_size/mtrr_chunk_size". I have been searching around and reading the kernel docs

At a number of sites we are using Windows 2000 Server SP4 (APPSERVER) as a Terminal Server and a PDC. All user areas are stored on a NetBSD 1.6.2 server with Samba 3.0.7 using security = domain and a named password server. We've joined the domain from the Samba box (domain DOMAINNAME). In general everything works fine, but when a number of clients log on at around the same time (say 25 users

I'm trying to rsync a very large (62gig) file from one machine to another as part of a nightly backup. If the file does not exist at the destination, it takes about 2.5 hours to copy in my environment. But, if the file does exist and --inplace is specified, and the file contents differ, rsync either is so significantly slowed as to take more than 30 hours (the longest I've let an

When a whole-file checksum is performed, hashing was done in 64 byte blocks, causing overhead and limiting performance. Testing showed the performance improvement to go up quickly going from 64 to 512 bytes, with diminishing returns above, 4096 was where it seemed to plateau for me. Re-used CHUNK_SIZE (32 kB) as it already exists and should be fine to use here anyway. Noticed this because

CentOS 6.4, current, Dell PE R720. Had an issue today with a bus error, and googling only found two year old references to problems with non-Dell drives (we just added two WD Reds, and mdadm raided them). So, looking through dmesg and /var/log/messages, I ran into a *lot* of G gran_size: 128K chunk_size: 256K num_reg: 10 lose cover RAM: 0G gran_size: 128K chunk_size:

We are using samba 3 on NetBSD with security=domain authenticating against Windows 2003. We have a username map of "root = administrator". In all previous versions of samba tested (2.2.x and 3.0.x), this means when we log on as administrator, we have root access and see the root share. With 3.0.10, we are continually prompted for a password. Log from 3.0.7 below: [2005/01/06 14:25:58,