similar to: [Bug 11] New: no reference to bugzilla on openssh home page

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

Maybe this is a ssh problem - but are you aware of the general issue ? http://bugzilla.mindrot.org/show_bug.cgi?id=182 Summary: ssh should still force SIGCHLD to be SIG_DFL when calling ssh-rand-helper Product: Portable OpenSSH Version: 3.1p1 Platform: ix86 OS/Version: All Status: NEW Severity: normal

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

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

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

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

http://bugzilla.mindrot.org/show_bug.cgi?id=132 ------- Additional Comments From dwd at bell-labs.com 2002-03-02 02:29 ------- Created an attachment (id=30) Patch against CVS of March 1, 2003 ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

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

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

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

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

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 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:

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 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

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

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/*

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