X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:mime-version:from:date:message-id:subject:to :content-type; q=dns; s=default; b=muZ4JGPGLssTp5YkaXH+8vCx9ItGY LbTm2VTYBvJA4ZRyVHHflTb1/SCkXD+wkwzwZ5b1SjzquAwcZ1jfa0UKKa8GF8n2 PEGXsGO0rH4yHA7Hjts/tN2hQDNy18bEMK+sz3GDVT/lHPCDaJsyT6XT0KTzfxlg kW+yrkNbYt7nn0= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:mime-version:from:date:message-id:subject:to :content-type; s=default; bh=ba4Upu903uOtGspV+Ik24YEpqGs=; b=Jf/ /qLVhDdWB9enU/duXQuzWXaZwC9SRXy9UpemHcBjep+PsTNT3W+JMbNNV2x85vt2 XjpnkguQD9mOUILr970JRRqPdvBeQxMUHLmCICEiG8gOMQLmWhg6pN6G46iXpcrb FVj0oOJT9A0+Dl38XKMMfHZqZpXC2lhcPki7MpNA= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.2 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.3.2 X-HELO: s87.webhostingserver.nl X-Received: by 10.112.141.193 with SMTP id rq1mr4211903lbb.25.1408711383186; Fri, 22 Aug 2014 05:43:03 -0700 (PDT) MIME-Version: 1.0 From: Frank Fesevur Date: Fri, 22 Aug 2014 14:42:33 +0200 Message-ID: Subject: rsyncd broken To: "cygwin AT cygwin DOT com" Content-Type: text/plain; charset=UTF-8 X-IsSubscribed: yes Jari, As I reported earlier rsync 3.1.0 is broken on cygwin. http://www.cygwin.com/ml/cygwin/2014-06/msg00212.html http://www.cygwin.com/ml/cygwin/2014-06/msg00442.html Any news on that issue yet? We run cygwin rsync daemons on our Windows servers and have a remote Ubuntu server that backups the important data using rsnapshot. Earlier this week I accidentally upgraded from 3.0.9 to your 3.1.0 on one of our servers and that night the backup failed with these (client side) error. @ERROR: setuid failed rsync error: error starting client-server protocol (code 5) at main.c(1653) [Receiver=3.1.0] ERROR: /usr/bin/rsync returned 5 while processing rsync://192.168.202.230/backup-d/DataWeb/ @ERROR: setuid failed rsync error: error starting client-server protocol (code 5) at main.c(1653) [Receiver=3.1.0] ERROR: /usr/bin/rsync returned 5 while processing rsync://192.168.202.230/backup-d/wwwroot/ I reverted to 3.0.9 and it works as expected again. But these error don't seem to be related to the 3.1.0 performance issues, so do you have any idea why it fails? Could the additional debian patch you've added cause this? I will try a self build vanilla rsync.exe 3.1.1 this weekend or early next week and see how that works. Regards, Frank -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple