similar to: Rsync 3.0.0 released

I've just released rsync 3.0.0pre10. I incorporated the latest daemon security fixes, and decided to include a few more minor bug fixes as well. If all goes well, this should be released as 3.0.0 final sometime next week. Please help to test it to ensure that we're ready to go! Send email to the rsync mailing list with your questions, comments, bug reports, etc. You can download the

I've just released rsync 3.0.0pre10. I incorporated the latest daemon security fixes, and decided to include a few more minor bug fixes as well. If all goes well, this should be released as 3.0.0 final sometime next week. Please help to test it to ensure that we're ready to go! Send email to the rsync mailing list with your questions, comments, bug reports, etc. You can download the

I've just released rsync 3.0.0pre1, the first pre-release version for the upcoming 3.0.0 release. The version number is getting such a large bump due to the addition of an incremental recursion scan (which helps a lot with large transfers) and the official arrival of several other new features, including ACL support, extended attribute support, file- name character-set conversion, etc.

I've just released rsync 3.0.0pre1, the first pre-release version for the upcoming 3.0.0 release. The version number is getting such a large bump due to the addition of an incremental recursion scan (which helps a lot with large transfers) and the official arrival of several other new features, including ACL support, extended attribute support, file- name character-set conversion, etc.

I've just released rsync 3.0.0pre7, the latest pre-release version of the upcoming 3.0.0 release. This release contains fixed exclude checks for a "use chroot = no" daemon that has excludes listed in the config file. This is a partial fix for the 2nd advisory that was released recently. See the rsync security web page for the updated details and a patch for 2.6.9:

I've just released rsync 3.0.0pre7, the latest pre-release version of the upcoming 3.0.0 release. This release contains fixed exclude checks for a "use chroot = no" daemon that has excludes listed in the config file. This is a partial fix for the 2nd advisory that was released recently. See the rsync security web page for the updated details and a patch for 2.6.9:

I have released rsync 3.0.1. This is a bug-fix release, which also includes fixes/improvements for several issues in the daemon-exclude code. To see a full summary of the changes since 3.0.0, visit this link: http://rsync.samba.org/ftp/rsync/src/rsync-3.0.1-NEWS You can download the source tar file and its signature from here: http://rsync.samba.org/ftp/rsync/src/rsync-3.0.1.tar.gz

I have released rsync 3.0.1. This is a bug-fix release, which also includes fixes/improvements for several issues in the daemon-exclude code. To see a full summary of the changes since 3.0.0, visit this link: http://rsync.samba.org/ftp/rsync/src/rsync-3.0.1-NEWS You can download the source tar file and its signature from here: http://rsync.samba.org/ftp/rsync/src/rsync-3.0.1.tar.gz

Hi, I'm very interested in learning the status of the --ignorecase patch being included in the main tree... is there a reason it still isn't in there? For anyone who is forced to dealing with backing up windows boxes, this is a big problem, and I can't believe that it isn't affecting a lot of people... Or maybe there is a simple workaround? I'm trying to backup files

Rsync version 2.6.1 has been released. It is primarily a performance release that requires less memory to run, makes fewer write calls to the socket (lowering the system CPU time), does less string copying (lowering the user CPU time), and also reduces the amount of data that is transmitted over the wire. There have also been quite a few bug fixes. See the release NEWS for the full details:

Rsync version 2.6.1 has been released. It is primarily a performance release that requires less memory to run, makes fewer write calls to the socket (lowering the system CPU time), does less string copying (lowering the user CPU time), and also reduces the amount of data that is transmitted over the wire. There have also been quite a few bug fixes. See the release NEWS for the full details:

I've just tried upgrading to cwrsync 2.1.0 (Rsync version 3.0.0 protocol version 30) between 2 Windows XP Pro sp2 machine across the Internet. I used: SET CYGWIN=nontsec SET HOME=c:\cwrsync\bin C:\cwrsync\bin\rsync -za -u -P --delete --recursive /cygdrive/c/test2/ stuart@test.address.co.uk::test/ When I run the above batch script on the remote machine I get this odd output.

Hi all! We're using cwrsync server 2.0.4 on winxp to keep files up to date between some operator machines. Whenever I run rsync to send files to another machine, the read-only flag gets set. The cwrsync user was created (the install is completely standard)... so I'm thinking it might have something to do with that. Here's my rsyncd.conf: use chroot = false strict modes = false

Yes this is another connection reset issue but all I am asking is some pointers on how I can possibly determine what and why this is happening. Its easy to say its a network issue but the bosses and clients want to know how to fix this said "network issue." I have read the rsync issues list. Some of what is suggested we might try HOWEVER we cannot duplicate the errors that occur and

I use rsync for backing up windows. After a restore of Desktop.ini I recognize that the hidden attribut and the system attribut will not been restored. I know, this are no unix attributes. But is there a way to backup and restore the windows attributes too? Thanks Matthias -- Don't Panic

I have set up an Rsync server on FreeBSD 5.3 and plan on having windows clients synchronize data to it. Rsync running as a daemon works fine. I can successfully copy data up to the server and view it via scp. Also- I can connect via ssh and run rsync as well. HOWEVER- I cannot connect "passwordless" with SSH and then connect to the rsync daemon. The following demonstartes what I

Hi gang. I am synchronizing Windows machines (cwRsync/cygwin) with FreeBSD server. A batch file is used to initiate the process (shell invoked rsync daemon). My question is whether I need to tell my users to close any affected applications (ex: Outlook; I am synchronizing the outlook.pst file) during the procedure? Peter __________________________________________________ Do You Yahoo!? Tired

I'm using CWRSync 2.6.9 protocol 29 on a Windows 2003 Standard R2 server. I'm trying to copy files onto a local usb harddrive. Both filesystems are NTFS. Rsync is failing to copy some files due to the file name length. I kind of assumed that Rsync could handle the same file name length that Windows users are allowed to enter. :-) Is there *anything* I can do with Rsync to allow these

Hi all, I'm rsyncing a windows 2003 client to a windows 2003 server using the cwrsync installation package. The trouble is that the permission rights set by rsync on the destination server are very restrictive and don't allow another application to access the files. I'd like to change that. However, the GID and UID parameters in the rsyncd.conf file don't seem to manage that.

I am trying to setup a windows 2000 server with rsync and cygwin. I think I almost have it working except that when the file copy is finished my files are nowhere to be found on the windows server. I am not getting any error messages. I am connecting from a win98 machine on the same network. Any ideas on how I can get this working or get more info to debug. Thanks.