search for: big1

...ich fail. I have started getting this error on very large modules since i moved to the latest CVS version. ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ToolSyncProgress Succeeded Getting big/tools/vlsi_local/etc from willy at 1004767211:2001:11:3:6:0:11. ToolSyncProgress Getting big1/cadappl1/hpux from willy at 1004767211:2001:11:3:6:0:11. rsync: connection unexpectedly closed (50466734 bytes read so far) rsync error: error in rsync protocol data stream (code 12) at io.c(139) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ The script checks exit status and retri...

...ng the week. They fail on different files. as you see, bildmax4 failed on only one file. bildmax2 failed on several screensful, but i trimmed it down. i don't see any duplication between systems. At the bottom, i show a ls of one of the files that failed on bildmax2, both on the master (/big1/....) and on the bildmax itself (/bildmax/bildmax2/...). What value is too big? Oh, the cmdline: /cadappl/encap/bin/rsync -Wa --delete --force --bwlimit=524288 source destination It's about 128Gb of data in about 2.8M files. Any idea what this randomness is? might the "Value too large...

...ood, 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 big1 = rnorm(size, 0, 1) big2 = rnorm(size, 0.5, 1 g1f = rep(1, size) g2f = rep(2, size) big = c(big1, big2) data_frame = data.frame(big, gr=as.factor(c(g1f, g2f))) wilcox_approx = wilcox.test(big1, big2) wilcox_exact = wilcox_test(big ~ gr, data=data_frame, distribution="exact") #---EndCode...

...drot.org ReportedBy: koenig at science-computing.de Hi OpenSSH, at least both openssh 3.5p1 and 3.6p1 give the wrong exit status 0 (zero) for "scp", if both source and destination are "remote" and some error happens (e.g. disk full): turtle tmp > scp /tmp/BIG1 /tmp/BIG2 ; echo $? cp: writing `/tmp/BIG2': No space left on device 1 turtle tmp > scp /tmp/BIG1 turtle:/tmp/BIG2 ; echo $? BIG1 100% |*****************************| 10601 KB 00:01 scp: /tmp/BIG2: No space left on device 1 turtle...

...drot.org ReportedBy: koenig at science-computing.de Hi OpenSSH, at least both openssh 3.5p1 and 3.6p1 give the wrong exit status 0 (zero) for "scp", if both source and destination are "remote" and some error happens (e.g. disk full): turtle tmp > scp /tmp/BIG1 /tmp/BIG2 ; echo $? cp: writing `/tmp/BIG2': No space left on device 1 turtle tmp > scp /tmp/BIG1 turtle:/tmp/BIG2 ; echo $? BIG1 100% |*****************************| 10601 KB 00:01 scp: /tmp/BIG2: No space left on device 1 turtle...

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

...sume that I do need to read in characters, and can't do any pre-processing of the file, etc. ## Create Sample File write.csv(matrix(as.character(1:1e6),ncol=10,byrow=TRUE),"big.csv",row.names=FALSE) q() **New Session** #R system("ls -l big.csv") system("free -m") big1<-matrix(scan("big.csv",sep=",",what=character(0),skip=1,n=1e6),ncol=10,byrow=TRUE) system("free -m") The file is approximately 9MB, but approximately 50-60MB is used to read it in. object.size(big1) is 56MB, or 56 bytes per string, which seems excessive. Regards,...

...-- Forwarded by Tim Conway/LMT/SC/PHILIPS on 04/17/2002 04:23 PM ----- "Sonu Singh" <sonu_mtl@hotmail.com> 04/16/2002 08:33 AM To: Tim Conway/LMT/SC/PHILIPS@AMEC cc: Subject: Re: rsync HELP!!! Classification: what is the [big] n [big1] u used? thanx >From: tim.conway@philips.com >To: "Sonu Singh" <sonu_mtl@hotmail.com> >CC: sarab@transbeam.com >Subject: Re: rsync HELP!!! >Date: Mon, 15 Apr 2002 13:58:01 -0600 > >Getting rsync to work is simple. What kind of system will you run it on? >Th...

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

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

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