similar to: timeout and process cleanup bugs 2.4.7pre1+

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

I see very odd results from rsync 2.4.7pre1, the latest cvs version (sept 12, i think was the last modified file). We have a number of network-attached storage devices. 10/100 ethernet, nfs2 mounted (under nfs3, they buffer deletes, and recursive deletions fail). Usually, these are kept syncronized across a wan by a nightly cronjob, We have a few we keep in reserve, which we syncronize

Sonu: I'm giving the whole history to the rsync list. If the tests i subscribed passed, yet you get that error, it's more in depth than i can go into. You've got 1 hour, let's hope somebody immediately recognizes the problem. I've got some ideas, but no time to explore any more for you. Gentlemen: does anybody see a quick resolution for Sonu? Looks like he's

Hello, I give you a little log format sample that I receive on the /var/log/rsyncd.log on the master server that receive data from a client : 2002/07/07 19:48:29 [15226] rsync to cfps from UNKNOWN (153.109.45.20) 2002/07/07 20:17:42 [15257] wrote 32 bytes read 1584410 bytes total size 5168179783 my problem : the ID task in the braket [] is not the same from the beginning and the end of the

I use FreeBSD RELENG_4 with rsync version 2.5.4 protocol version 26 Copyright (C) 1996-2002 by Andrew Tridgell and others <http://rsync.samba.org/> Capabilities: 64-bit files, socketpairs, hard links, symlinks, batchfiles, IPv6, 32-bit system inums, 64-bit internal inums and when I try to transfer file I get rsync: connection unexpectedly closed (5994 bytes read so

This is my first post so first of all I will say hello to everyone. I have rsync configured and working properly on my local network however when I try to connect from a remote host (one located in a different state) the connection times out. I was wondering if there was another way to set the timeout besides in the rsyncd.conf file? As I said the connection works fine on the internal lan, but

Hello All, I have searched for this error and found similiar errors, but everything seems to indicate that this should be fixed in the 2.5.5 version. rsync version 2.5.5 protocol version 26 I am running rsync with -axz, trying to sync up a large gz file : Source machine: -rw-r--r-- 1 root other 175214792 Dec 22 00:17

Is it true that when running rsync via ssh (i.e. rsync -e ssh ...) the rsyncd.conf file is not applicable on the remote since rsync is launched via the ssh exec call once connected rather than from rsyncd as in a direct connect. If so, I am trying to find the best way to restrict rsync -e ssh on the remote machine. Prepending the authorized_keys entry with command='rsync ...' 1024...

Hi, I became a little bit confused when working with the Wilcoxon test in R. As far as I understood, there are mainly two versions: 1) wilcox.test{stats}, which is the default and an approximation, especially, when ties are involved 2) wilcox_test{coin}, which does calculate the distribution _exactly_ even, with ties. I have the following scenario: #---BeginCode--- # big example size = 60

Hi, I've been having similar experiences and haven't been able to substantially improve the efficiency using the guidance in the I/O Manual. Could anyone advise on how to improve the following scan()? It is not based on my real file, please assume that I do need to read in characters, and can't do any pre-processing of the file, etc. ## Create Sample File

http://bugzilla.mindrot.org/show_bug.cgi?id=639 Summary: scp: wrong exit status Product: Portable OpenSSH Version: 3.6.1p2 Platform: All OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: scp AssignedTo: openssh-bugs at mindrot.org ReportedBy: koenig at

http://bugzilla.mindrot.org/show_bug.cgi?id=638 Summary: scp: wrong exit status Product: Portable OpenSSH Version: 3.6.1p2 Platform: All OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: scp AssignedTo: openssh-bugs at mindrot.org ReportedBy: koenig at

Salim: I suspect that if you check the timestamp, you'll find that that binding failure is left over from an earlier attempt, before you were properly configured. Your description of you inetd.conf/services setup sounds correct. Your commandline, though, shouldn't work. You name a directory as the source, but don't say to do its contents. However, I would expect an error from

I?m trying to rsync a 210 GB Filesystem with approx 1.500.000 Files. Rsync always dies after about 29 GB without any error messages. I?m Using rsync version 2.5.5 protocol version 26. Has anyone an idea ? Thank?s Clemens

When rsync starts I get the following messages in my log file Jan 11 11:00:04 WEB1 rsyncd[31281]: rsync: bind failed on port 873 Jan 11 11:00:04 WEB1 rsyncd[31281]: rsync error: error in socket IO (code 10) at socket.c(361) Anybody know what might be causing this? David