similar to: one more day of delay for release of 2.5.6

The second rsync-2.5.6 pre-release version is now available at: http://rsync.samba.org/ftp/rsync/preview/rsync-2.5.6pre2.tar.gz ftp://rsync.samba.org/pub/rsync/preview/rsync-2.5.6pre2.tar.gz rsync://rsync.samba.org/ftp/rsync/preview/rsync-2.5.6pre2.tar.gz There's also a corresponding '.sig' file that contains a gpg signature of the file; the public key is available on the

Rsync release 2.5.6 is now available at http://ftp.samba.org/ftp/rsync/rsync-2.5.6.tar.gz ftp://ftp.samba.org/pub/rsync/rsync-2.5.6.tar.gz rsync://ftp.samba.org/ftp/rsync/rsync-2.5.6.tar.gz There is a '.sig' file at corresponding URLs with a gpg signature; the public key is available on the pgp keyservers. NEWS for rsync version 2.5.6, aka the dwd-between-jobs release Changes

The first rsync-2.5.6 pre-release version is now available at: http://rsync.samba.org/ftp/rsync/preview/rsync-2.5.6pre1.tar.gz ftp://rsync.samba.org/pub/rsync/preview/rsync-2.5.6pre1.tar.gz rsync://rsync.samba.org/ftp/rsync/preview/rsync-2.5.6pre1.tar.gz There's also a corresponding '.sig' file that contains a gpg signature of the file; the public key is available on the

I had a friend run some Cygwin tests and we found that --modify-window=1 works just as well as --modify-window=2 on FAT filesystems to copy files from Unix and detect the difference in granularity. FAT filesystems always have timestamps that have an even number of seconds. On the other hand, NTFS filesystems can store the modification time down to the second, whereas previously people on this

I'm working on trying to get rsync 2.5.6pre1 available for people to test more widely. I'm out of time for today, and I'm stuck on a problem that some machines on build.samba.org are showing on the 'chgrp' test. I can reproduce this on my home redhat 7.3 system too. It appears to be a timing problem because when I do strace -F -f on it the problem goes away. Everything seems

When using Cygwin Rsync 2.5.6/OpenSSH 3.6.1 for copying files from Win2k->Win2k, I get 2 or 3 hung processes on the receiving-side out of about every 50 runs. These hung processes cause the system to be unable to reboot(?!), requiring a hard reset. Killing the processes allows a graceful reboot every time. I'm currently running both ssh and rsync as services on the recieving side.

Hi. On the one hand, I don't want to annoy anyone with repeated emails :-), but on the other, I would like to know the chances of the patch making it in to 2.5.6. Even if the answer is 'Maybe - too busy to think about it right now', I will be satisfied, but if I need to revise it before it can be considered, I would like to know that. Max.

We have AIX 4.3.3 ML09 and AIX 5.1 ML01 I have narrowed the problem down, it is nothing to do with uni/multiprocessor machines. Both rsync 2.3.1 compiled by Bull in an installp and a gcc compiled version of 2.4.5 ( by me ) both have exactly the same problem with SSH 3.1.p1 and both DONT have the problem with SSH 2.9.9p1 - so I assume this is something highly specific to SSH 3.1.1.p1 Hope this

I have been trying to get rsync running correctly on cygwin for the past couple of days. I found a post on the cygwin list that said there was a bug in cygwin when using socketpair() but when I compiled the sample code: (http://jrepp.com/rsync/socketpair.c) both ways it works fine. Here's the article for reference: http://sources.redhat.com/ml/cygwin/2001-08/msg00357.html I am running the

rsync 2.5.6 is hanging in cygwin, at the end when it should print a summary of bytes sent etc and exit. It has successfully copied all the files before hanging. It does this every time when copying to or from a Windows share. (It sometimes hangs when copying from one local drive location to another, but I have not tested this as thoroughly.) The Windows shares are almost certainly on Windows

Bugzilla doesn't appear to send new bugs to openssh-unix-dev as Damien said he wanted it to, so I'm forwarding the message I got back. - Dave Dykstra ----- Forwarded message from bugzilla-daemon at mindrot.org ----- From: bugzilla-daemon at mindrot.org To: dwd at bell-labs.com Subject: [Bug 11] New: no reference to bugzilla on openssh home page Date: Sat, 10 Nov 2001 03:55:32 +1100

Does rsync has directory name length limit? I was trying to rsync a directory that has the name length of 34 characters and getting permission denied error. $ rsync -avz --delete --force -e ssh /usr/local/apache/htdocs 192.168.0.2:/usr/local/apache building file list ... readlink htdocs/CorporateLegalTimesEDITORIAL_files/cBug_blueXs.gif: Permission denied readlink

On 6 Dec 2001, Dave Dykstra <dwd@bell-labs.com> wrote: > I still hope to write a --files-from option sometime in 2001. Excuse me if I've forgotten something from earlier: what happens when the sender is remote? Do we send the contents of the file list across along with the arguments, or does this option not work in that case, or is the file named to be opened on the remote

On Tue, Nov 27, 2001 at 01:22:43PM -0800, Simison, Matthew wrote: > turns out, I have an rsync virtual site builder script, which makes the new > user > conf file run with perm 400. And apparently someone thought that the main > rsyncd.conf file needed to be the same, and that killed all connections. > > Sorry for bothering. > > Matt > > -----Original Message-----

Not sure, I am re-running this to ensure that I was not smoking crack at the time :) > -----Original Message----- > From: Dave Dykstra [mailto:dwd@bell-labs.com] > Sent: Thursday, November 29, 2001 1:12 PM > To: Keating, Tim > Cc: rsync@samba.org > Subject: Re: Rsync: Re: patch to enable faster mirroring of large > filesyst ems > > > On Thu, Nov 29, 2001 at

Dave- I've got the rsync daemon running as root, (setgroups() man page said that if setgroups wasn't called as root it would give an error message) and I've configured the ports correctly a la man page. I still get the error with setgroups. If it's a recently implemented security feature could I yank that section out of the code and recompile it again? I haven't had a chance to

Martin, I want to remind you that there's still an open issue regarding copies when both source and destination are on the local machine (including over NFS): I put a patch into the CVS to automatically imply the '-W' option in that case, and somebody said he was concerned about that because he found that with -W on local copies he had cases where rsync would lock up, and it

Hi, In http://sources.redhat.com/ml/cygwin/2002-09/msg01155.html, I noted that the often-observed hangs of rsync under Cygwin were assuaged by a call to msleep(). After upgrading my Cygwin environment to rsync 2.5.6, I'm seeing these hangs again, not surprisingly given a CVS entry for main.c notes that this kludge was not harmless: Revision 1.162 / (download) - annotate - [select for

I am copying from a rsync --daemon (have tried from both W2K/cygwin & Linux daemons) to a W2K machine. Some files get copied every time even though they haven't been touched since the last copy. I have experimented and deturmined that the file size seems to be important. If the file is between 926 & 933 bytes long it will always be copied!! Other sizes and possibly other aspects of

Hi, though the list would be interested to know an issue we have just come across. We have found that rsync version 2.5.6 over ssh within a cygwin environment run manually from either a command prompt or a cygwin prompt hangs every time if we run it in a Windows Terminal Server session. It doesn't seem to matter what the remote server is as we have experienced this when the remote server is