similar to: open issue regarding local copies and -W

Hello All: I've having repeatable problems copying files between linux machines using rsync-2.5.1 and various recent flavors of openssh. The symptom when testing with a single 2M file is that rsync hangs when when the file is 97% transferred. It seems from looking at various archives that this problem may be non-trivial. I tried applying the patch at

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

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

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

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

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

I'd like to revisit the topic of moving files from system to system using rsync. I've just updated my patch from its 2.5.0 version to 2.5.1, and I'm curious what people think about getting it integrated into rsync. The patch comes in two parts. The first eliminates a potential hang condition that can happen if the data channel from the receiver to the generator gets clogged up.

I am trying to finalize the use of rsync for updatiung a new nfs server before we take the old one offline. I keep getting the following warning during the rsync process: Warning: unexpected rad size of 0 in map_ptr Any ideas where this comes from and how to make it go away? I am using rsync 2.5.2 on Solaris 8 to pull data from rsync 2.5.2 on Solaris 7. Bob roconnor@vectorpartners.com

Hi, I got stuck within some weird prob concerning my 2-node linux cluster and the synchronisation tool at hand (rsync-2.5.1pre1). I have to copy a structure of 70 directories where the data of these directories are hardlinked to the data of the 1st directory. Within this "orig data" directory, I have about 30.000 files, so the amount of files to sync is approx. 2.100.000. 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

On Thu, Jan 13, 2000 at 17:34:10, Andre Lucas wrote: > Subject: /dev/urandom > On Thu, Jan 13, 2000 at 09:24:01AM -0700, SysProg - Nathan Paul Simons wrote: > > On Thu, 13 Jan 2000, Ben Taylor wrote: > > > > > On Thu, 13 Jan 2000, Max Shaposhnikov wrote: > > > > why ssh1.27 doesn't requre /dev/urandom on solaris? > > > > i think the

Howdy, We occassionally get the following error when running our nightly backups: rsync error: received SIGUSR1 or SIGINT (code 20) at rsync.c(229) This happens more on one or two machines than on any of the others. We've looked high and low to see if we're mistakenly sending these signals, but nothing is that we can find. Does anyone know what this might be from? Is it the server

Does it bother anybody else that -v prints directories twice? It first prints all affected directories and files in recursive order and then prints new directories again. I can't recall noticing that rsync always did that, but I don't think it's a very recent change. The directory is being printed both times by recv_generator(), and I checked CVS and it's been there since the

I want to rsync only a small part of a directory tree. I've set up an exclude and an include file: exclude holds: /* include holds: /iso/1.5.*/i386 I am calling rsync using rsync -avz --include-from="include" --exclude-from="exclude" ftp3.sourceforge.net::/netbsd/iso iso/ but nothing happens. No files transfered. But I would expect rsync to transfer files:

That's the way it is. If it's really a one-off change, a huge change in your structure, telnet ssh, rsh, and so forth, work really well for dropping in and deleting stuff (unless you're supplying the master, and other systems out of your control copy from you). Rsync is optimized for taking a filesystem in an unknown state, and making it identical to another filesystem in an unknown

I get the following log messages using rsync 2.5.1 compiled on Solaris 8 when using the "hosts allow" option in rsyncd.conf: 2002/01/23 12:09:51 [28276] rsync: reverse name lookup mismatch on fd0 - spoofed address? 2002/01/23 12:10:18 [28276] rsync: connection unexpectedly closed (16 bytes read so far) Resolv.conf/DNS are configured and working properly with both A and PTR records

I just ran this again and got this error: leelab/NCBI_Data_old/GenBank/htg write failed on leelab/NCBI_Data_old/GenBank/htg : Error 0 rsync error: error in file IO (code 11) at receiver.c(243) Received signal 16. (no core) rsync error: received SIGUSR1 or SIGINT (code 20) at rsync.c(229) The command I am running is: /usr/local/bin/rsync -auv --delete --rsh=/usr/bin/ssh lpgfs104:/share/group/*

Hello, I have set up an anonymous rsync server that seems to work as expected. However when I try to access the server from several other unix boxes using rsync with a command like this; rsync netlib3.cs.utk.edu::netlib I get the motd and then a line that states client: nothing to do Now I would expect this to give me a directory listing. I do get the directory listing as expected when

@ERROR: failed to open lock file /var/run/rsyncd.lock : No such file or directory solaris 2.6 (server) rsync 2.3.1 this has never been a problem before. This is a customer's error when trying to upload to our server. They claim it is not their end. I disagree. Anyway, I don't have their version info or OS. Matt

Well, here's rsync 2.4.7 preview 1: rsync://va.samba.org/ftp/rsync/preview/rsync-2.4.7pre1.tar.bz2 http://va.samba.org/ftp/rsync/preview/rsync-2.4.7pre1.tar.bz2 You need bunzip2 to decompress these files: http://freshmeat.net/projects/bzip2 The change list is below. Please, do try this out and let us know either if it works for you or if it does not. We need both kinds of