similar to: Weird differing results when using the Wilcoxon-test

I appear to be seeing the performance of a local ZFS file system degrading over a short period of time. My system configuration: 32 bit Athlon 1800+ CPU 1 Gbyte of RAM Solaris 10 U6 SunOS filer 5.10 Generic_137138-09 i86pc i386 i86pc 2x250 GByte Western Digital WD2500JB IDE hard drives 1 zfs pool (striped with the two drives, 449 GBytes total) 1 hard drive has

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

I have written an application in perl, to run multiple rsyncs, retrying those which 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

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

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

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

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

From: Anastasiia Lukianenko <anastasiia_lukianenko at epam.com> We are trying to use the clang-format approach as a base for Xen [1] style formatting. During the state of testing clang-format with different configurations, we found that some points regarding the Xen coding style are not configurable. Therefore, we decided to add them to be able to make a choice in different cases. Regards,

> Here's the deal... I have a filesystem that I have populated by > rsyncing from a filer (over NFS) using the --link-dest option to create > incremental "snapshots" of the live data. This part is working > fine... lots of links, much fewer blocks represented. Now it is time > to migrate to > a larger filesystem and, during the rsync, the links are not being

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

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

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

I have an OS X 10.4 Server machine that has abysmal performance when copying files to it over smbmount from a linux machine or through Finder on OS X but performs very well when copying files through smbclient from the same Linux and OS X machines. I have already tried the commonly suggested adjustment of net.inet.tcp.delayed_ack=0 and have not noticed a significant performance improvement.

> You don't. Audio CDs don't support ReplayGain tags. The only thing > you may do on Audio CDs is to use Volume Normalize techniques > available on certain programs. Normalization of sound is not a good, > clean thing, though. Surely it would be possible to have something apply the ReplayGain to the WAV after decoding and prior to writing them to CD... but I don't know

* * * This series of VSOCK linux upstreaming patches include latest udpate from VMware. Summary of changes: - Sparse clean. - Checkpatch clean with one exception, a "complex macro" in which we can't add parentheses. - Remove all runtime assertions. - Fix device name, so that existing user clients work. - Fix VMCI handle lookup. * *

* * * This series of VSOCK linux upstreaming patches include latest udpate from VMware. Summary of changes: - Sparse clean. - Checkpatch clean with one exception, a "complex macro" in which we can't add parentheses. - Remove all runtime assertions. - Fix device name, so that existing user clients work. - Fix VMCI handle lookup. * *

On 29 February 2012 09:35, Chandler Carruth <chandlerc at google.com> wrote: > I still think we can do more, but it's already much faster than the existing LLVM one except for the issue Tobias pointed out w/ modulo-4 key sizes. I'm going to investigate this OK, but this is a VERY big exception! Almost any non-string data anyone wants to hash will be a multiple of 4 bytes in