similar to: 2.6.0 backwards compatibility

Running on a Debian server, 3.0r Sid, 2.4.18 kernel. I recently did an apt-get upgrade which upgraded samba from 3.0.5 to 3.0.6 After this upgrade, access to all shares for all users slowed to a crawl. It was possible to browse the folders, to 3-4 folders deep but then Explorer would freeze on the client.Opening files failed. Copying files locally resulted in corrupt files. Clients included

Tevfik On Tuesday 09 Dec 2003 18:13, Tevfik Karag?lle wrote: > I would also like to inform that I updated my cwRsync package with the > latest rsync binary (2.5.7). http://itefix.no/cwrsync I have tried your rsync 2.5.7 in cygwin under Windows 2000, synchronising to a windows share on an unknown (probably Windows) file server. Sorry to report that it hangs at the end of transfer, as did

Hi everyone. Has anyone experienced rsync 2.6.0 causing huge amounts of system load? Especially on Linux 2.4? We recently upgraded our "push" machine to rsync 2.6.0 and the next push that went out (rsyncing about 3GB of data to 15 servers sequentially over gigabit ethernet) caused the box to hit 110.59. We only know the load because snmpd was still working, but nothing else in userspace

The changes made to 2.6.0pre1 have been pretty minor so far, so I had been debating whether we needed a pre2 release or not. I finally decided to go ahead and release what little there is, just to give folks a final opportunity to double check the final release: http://samba.org/ftp/rsync/preview/rsync-2.6.0pre2.tar.gz http://samba.org/ftp/rsync/preview/rsync-2.6.0pre2.tar.gz.sig

On Mon, 10 Nov 2003, Wayne Davison <wayned@samba.org>?wrote: > >?... This fix is also in CVS (along with several others). As another poster pointed out recently, it's been a long time since 2.5.6 was released (Jan 28 2003). Many recent replies to questions posted to this list are variants of "It's already fixed in CVS". Are there any particular reasons for holding

Hi, I am running rsync version 2.5.7 (stock distro on redhat linux, ES and 9) to rsync a directory with ~300k files in it from a machine on a 10Mbit internet tap to a machine with a 100Mbit internet tap. The problem is that I am only getting about 500Kbps during the transfer. I have tested link speed by scping a file between the two systems, performance was approximately 7.5Mbit/sec. Ping time

I'm using server on OpenBSD 3.4 to backuping data from remote server via rsync.On backup server I am install rsync-2.5.6 and on remote machine rsync-2.5.7 (RedHat 8.0) . For backuping data I'm using the following command : rsync -av -e ssh backup@log:/var/backup/ALL-15-Mar.tar /var/backup/3 This command copy file ALL-15-Mar.tar from host log(RedHat box) to local directory on OpenBSD.

During my initial download for my home directory backup, it took rsync over 6 hours to do the initial backup, but I can FTP the stuff in about 30 Mins. Is Rsync usualy this slow? I have compression turned on, and its across a 100 MB/S network, Anyone had this problem before? Steve Sills

One thing that's bugged me is that some of the man page lines in the options summary are longer than 79 chars and wrap onto the next line. These are just one line summaries (detailed description appear later) so they can, and should, be terse. Here's an edited diff showing my proposed changes (and a 79 char ruler):

rsync 2.5.6 security advisory ----------------------------- December 4th 2003 Background ---------- The rsync team has received evidence that a vulnerability in rsync was recently used in combination with a Linux kernel vulnerability to compromise the security of a public rsync server. While the forensic evidence we have is incomplete, we have pieced together the most likely way that this

rsync 2.5.6 security advisory ----------------------------- December 4th 2003 Background ---------- The rsync team has received evidence that a vulnerability in rsync was recently used in combination with a Linux kernel vulnerability to compromise the security of a public rsync server. While the forensic evidence we have is incomplete, we have pieced together the most likely way that this

I am looking to upgrade to latest version of rsync. However there are some critical bug fixes (for my needs) that have been commited to CVS post 2.5.6 release. Can anyone tell me how i can find out the release schedule for 2.5.7? I looked around at rsync home page and did not see how i can access schedule/timeline for official releases. I can work with latest in CVS if the release date is too

> On Wed, Sep 03, 2003 at 03:49:12PM -0400, Matt Miller wrote: >> I have seen this error in many postings, but the solutions seem not to >> apply in this case. This error happens during a small file transfer >> (gif image) and after 75% of a 165G rsync job (the building file list >> portion is complete.) Most solutions I saw were related to not having >>

Hi, I’ve noted some change in wording on the current (4.0) developer policy[1], compared to the 3.9 developer policy[2]. Specifically the part about IR Backwards Compatibility. The change from 3.9 to 4.0 is the following: - The textual format is not backwards compatible. We don’t change it too often, but there are no specific promises. - Additions and changes to the IR should be reflected

I develop GNU Parallel. GNU Parallel uses rsync to transfer files. GNU Parallel has a design goal of not requiring the users to change their setup to be able to use GNU Parallel. In other words: If you are called as a consultant to work on a Centos3 server untouched since 2007, then you can expect even the newest version of GNU Parallel will work flawlessly. Centos3 has rsync 2.5.7 installed. On

What I want to do is use rsync to back up a folder to an external drive. I would like to keep 30 days worth. For example: I have backups of June 1 - June 30. Once July 1 comes along, I want to keep June 2 - July 1 and delete June 1, and so forth. Any ideas how I can accomplish this? -- View this message in context: http://www.nabble.com/Rysnc-Schedule-tf4104577.html#a11672997 Sent from the

I am attempting to use rsync to backup a Win98 laptop to a FreeBSD 4.8 backup server. I have experienced the same problem at roughly the same point in the process on two occations. The laptop contains ~2.7Gb of data. On the first attempt we received this error at 2.3Gb and on the second at 2.4Gb. rsync error: partial transfer (code 23) at main.c(575) Would love to have a full backup of the

Hi, What are the limits to file size and file count when doing a rsync transfer using 2.5.6? I was trying to rsync about 500 GB of data with many files and many directories, but it has been stuck building the file list for several hours. First of all, is it possible to transfer 500 GB of data? Secondly, what would the limit for file count be when doing a rsync transfer? Any comments or help

Hi all - I've got two red hat linux 7.3 systems. On each i have the redhat-provided 2.5.7 in the standard location, and a locally built copy of 2.6.1 in /usr/local/pkg. I'm implementing a remote-backup-to-disk setup. blakey is the "client" (source of rsync), verve is the "server" (dest of rsync). When i take care to match rsync binary versions (2.5.7 on each

A new 2.6.0 feature is supposed to use a different exit code when the only 'errors' were from files that disappeared between the building of the file list and the actual transfer of files. But if the client is local and the server is remote, IOERR_VANISHED gets set on the remote server, but is never passed to the local client (the io_error value is passed at the end of the file list, not