Re: Do you like rsync 2.5.5?

On Wed, Apr 03, 2002 at 03:57:32PM +1000, Martin Pool wrote: > On 2 Apr 2002, Albert Chin <[EMAIL PROTECTED]> wrote: > > On Wed, Apr 03, 2002 at 10:14:50AM +1000, Martin Pool wrote: > > > Are there any other patches you think really need to go into a 2.5.6 > > > before we proceed? > > > > Th

Re: Do you like rsync 2.5.5?

On 2 Apr 2002, Albert Chin <[EMAIL PROTECTED]> wrote: > On Wed, Apr 03, 2002 at 10:14:50AM +1000, Martin Pool wrote: > > Are there any other patches you think really need to go into a 2.5.6 > > before we proceed? > > The attached patch is important for "out of the box" compilation on > Tru64

Re: Do you like rsync 2.5.5?

On Wed, Apr 03, 2002 at 10:14:50AM +1000, Martin Pool wrote: > Are there any other patches you think really need to go into a 2.5.6 > before we proceed? The attached patch is important for "out of the box" compilation on Tru64 UNIX. The FreeBSD issue has been resolved. -- albert chin ([EMAI

Re: getaddrinfo() problem with AIX 4.3.3 and rsync 2.5.2?

On 1 Apr 2002, "Allen, John L." <[EMAIL PROTECTED]> wrote: > I had to apply the following patch to the clientname.c check_name() function > before I could successfully use "hosts allow" in rsyncd.conf. Without the > patch I kept getting "rsync: forward name lookup for ... failed: Host not > foun

Re: Do you like rsync 2.5.5?

On 2 Apr 2002, Eric Whiting <[EMAIL PROTECTED]> wrote: > Do I need to have 2.5.5 on both ends of the rsync (via ssh) to provide > useful test results? Results for both cases are useful, because we want to preserve backward compatibility. For example, if rsync 2.5.5 - 2.4.6 hangs, then I woul

Re: Do you like rsync 2.5.5?

Martin Pool wrote: > Has anybody tried 2.5.5? Did it work well? I ran it last night on about 400 trees. It seemed to timeout improperly. I'll have more data on this tomorrow. Timeout was set at 1000 and it seemed to timeout more than I've seen before (about 50 of the trees reported timeouts).

Do you like rsync 2.5.5?

I'd very much like to get a stable 2.5 release out so that people can upgrade their production machines with confidence and so that distributors can freeze it. I know some people are still running 2.4.6 (+backports) for understandable reasons, but it would be good to give them the option to upgra

Re: metadata in dryrun mode

On 2 Apr 2002, Mark Santcroos <[EMAIL PROTECTED]> wrote: > As I reported a while back rsync doesn't handle metadata (permissions and > ownership) in dryrun mode. > > I offered to make a patch and that offer still stands. I didn't have the > time for it until now and want to pick it up again. I h

Re: (fwd from flepied@mandrakesoft.com) rsync dead loop

On Sat, Mar 16, 2002 at 10:19:56AM -0800, Martin Pool wrote: > On 16 Mar 2002, Martin Pool <[EMAIL PROTECTED]> wrote: > > > While testing a frontend to rsync, we have been bitten by rsync eating > > all the memory of the host. We have found that it was due to rsync > > trying to write an error an

metadata in dryrun mode

As I reported a while back rsync doesn't handle metadata (permissions and ownership) in dryrun mode. I offered to make a patch and that offer still stands. I didn't have the time for it until now and want to pick it up again. I had some ugly hack back then but I want to redo it in a clean way. I

Re: error in rsync protocol data stream (code 12) at token.c(288)

While this does appear to work in 2.5.4, I suspect that is because of the 2.5.4 whole-file bug. With 2.5.5 it fails again, with the following error message: deflate on token returned 0 (16384 bytes left) rsync error: error in rsync protocol data stream (code 12) at token.c(288) According to sba

RE: getaddrinfo() problem with AIX 4.3.3 and rsync 2.5.2?

Yes, I had to put "rsync873/tcp" in /etc/services to make it work at all, but that still didn't help fix this particular problem. As I said, it was passing a large port number to getaddrinfo(), one that's clearly the client side of a socket connection, and one that is not going to be in

Re: getaddrinfo() problem with AIX 4.3.3 and rsync 2.5.2?

I have built rsync on Irix 6.5, Fujitsu something, AIX 4.3, Sus Linux 7.x, HPUX something. The only one I've had a problem with is AIX 4.3. IBM tell me getaddrinfo is working as designed and that the port number must be assigned in the /etc/services file. I can't see why this should be so, but the

rsync 2.3.2 with --copy-unsafe-links work badly

Hello, I try use rsync from Debian 2.2 (rsync 2.3.2) to mirror Debian distribution tree. in tree is directories dists/potato/main/binary-all/ dists/potato/main/binary-i386/ pool/ In directory dists/potato/main/binary-i386/ is some files symbolic links to ../binary-all/ and some links to ../../