similar to: [Bug 2187] rsync large file getting verification failed using -z

https://bugzilla.samba.org/show_bug.cgi?id=2187 ------- Additional Comments From qiucheng@csc.com.cn 2004-12-27 01:15 ------- Created an attachment (id=869) --> (https://bugzilla.samba.org/attachment.cgi?id=869&action=view) error log -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact

Hi, I think I found a bug in usage of zlib. rsync 2.5.6 with -z fails like bellow. % cp install-disk2.iso /var/tmp/install-disk2.iso install-disk2.iso 100% |*****************************| 316 MB 00:56 % rsync -vIz install-disk2.iso 127.0.0.1:/var/tmp/install-disk2.iso install-disk2.iso deflate on token returned 0 (16384 bytes left) rsync error: error in rsync protocol

https://bugzilla.samba.org/show_bug.cgi?id=3925 Summary: rsync is unable to sync large (approx 4G) sparse files Product: rsync Version: 2.6.8 Platform: x86 OS/Version: Linux Status: NEW Severity: major Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy:

https://bugzilla.samba.org/show_bug.cgi?id=14338 Bug ID: 14338 Summary: ZSTD support Product: rsync Version: 3.1.3 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 Component: core Assignee: wayne at opencoder.net Reporter: Rsync at ml.breakpoint.cc

Hi all, The firmware I used is pa168s_iax2_us_151011.bin. My problem is the handset dial before I finished key in all the numbers, no matter how fast I managed to press the keys. It appeared it always dialed immediately, for example "011862", when I actually ment to dial 0118620xxxxxxxx. Thus left the remaining numbers "0xxxxxxxx" unsent. The handset had its dial plan

https://bugzilla.mindrot.org/show_bug.cgi?id=2187 Bug ID: 2187 Summary: ssh-add unnecessarily prompts for PKCS#11 pin when removing key Product: Portable OpenSSH Version: 6.3p1 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 Component: ssh-add

I just got done sending 42,000 e-mail messages that were rotting away in /var/spool/clientmqueue. I figured out the command to do so was "sendmail -L sm-msp-queue -Ac -q30m". I never even knew that directory existed. I thought everything queued was kept in /var/spool/mqueue (which, I might add is being taken care of on a regular basis.. just seems the problem lies in the

https://bugzilla.samba.org/show_bug.cgi?id=6916 Summary: Avoid bundling a modified zlib Product: rsync Version: 3.1.0 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P3 Component: core AssignedTo: wayned at samba.org ReportedBy: matt at mattmccutchen.net

On Sun, Feb 24, 2002 at 09:04:03AM +0100, Ricardo Galli wrote: > Sorry, didn't explain well. > > Nagle's algorithm (rfc896) buffers user data until there is no pending acks > or it can send a full segment (rfc1122). > > icecast doesn't need it at all, because it already sends large buffers and > the time to send the next buffers is relatively very long. IMO

I am using rsync version 3.0.7. My rsync server is running on the cloud. I have set the bwlimit to 10 i.e. 10 KBps. When I try to sync files the bwlimit is as what is set. I have enabled storage of partial files. When a communication break causes rsync to time out during a transfer the partial file is stored in the partial directory. I then try rsync again when the link is up. At this point I see

I am experiencing intermittent network failures on rsync 3.0.7 built using cygwin for Windows-XP (SP2). I am using GCC v4.4.2 and the latext version of cygwin. The rsync error long indicates things like: rsync: writefd_unbuffered failed to write 4092 bytes to socket [generator]: Connection reset by peer (104)rsync: read error: Connection reset by peer (104) rsync error: error in rsync

https://bugzilla.mindrot.org/show_bug.cgi?id=3475 Bug ID: 3475 Summary: ED25519 signature verification nondeterministic spurious failure Product: Portable OpenSSH Version: v9.0p1 Hardware: amd64 OS: Linux Status: NEW Severity: critical Priority: P5 Component: ssh

https://bugzilla.samba.org/show_bug.cgi?id=14390 Bug ID: 14390 Summary: Feature request: don't fail if using "-z" transferring to rsync complied with --with-included-zlib=no Product: rsync Version: 3.1.3 Hardware: All OS: All Status: NEW Severity: enhancement

---------- Forwarded message ---------- From: Jan Prunk <janprunk at gmail.com> Date: Sep 13, 2007 3:35 PM Subject: Bad FCS error To: asterisk-users at lists.digium.com Hello ! I am getting the following error in asterisk logs: Sep 11 17:33:30 NOTICE[2187] chan_zap.c: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1 Sep 11 21:45:08 NOTICE[2187] chan_zap.c: PRI got event:

Hello! What is the simplest way to make merb respond to the client sending Accept-Encoding: gzip? Just checking if it exists, otherwise I''ll implement it myself. Regards, Magnus

Hello, I want to use rsync to create backups. I think I need a verification that: 1) data is written to disk. 2) data is read back from disk. 3) verify the checksum of data. Does the automatic file verification in rsync works like this? Technically, I'd like to know how does we make step 2 read data from disk and not from file cache/buffer in OS? Or, do OS/harddrives always perform written

http://bugzilla.mindrot.org/show_bug.cgi?id=734 Summary: Misleading error message when host key verification is impossible / SSH_ASKPASS impossible. Product: Portable OpenSSH Version: 3.6.1p2 Platform: All OS/Version: Linux Status: NEW Severity: trivial Priority: P5 Component: ssh

Hi, I tried executing the rpm -V command on the packages of the CentOS 7.2 ISO which I have created, the verification failed for some of them. Here is the log for 'authconfig' : Steps: 1. Execute command : rpm -V authconfig 2. Observe the output Expected Result: If there is no error, nothing should be displayed Actual Result: Verification fails with following error log:

Hi, I see some warnings like the following. Could anybody explains what they mean? Thanks. 19/31274477.pdf 257,169,119 0% 1.26MB/s 0:03:15 (xfr#121, to-chk=848309/1043298)WARNING: 18/32281577.pdf failed verification -- update retained (will try again). WARNING: 19/28879866.pdf failed verification -- update retained (will try again). -- Regards, Peng

Dear R developers, it seems that I am in the mood of filing bug reports. Partly because R-1.0 is approaching fast, partly to explain why I have send (yet) another empty bug report. My settings are as follows: > options()$mailer [1] "mailx" > options()$method NULL > options()$editor [1] "emacsclient" My first attempt to send the last bug-report about "R CMD