From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: rsync failed after windows 10 update
Date: Wed, 06 Mar 2019 11:57:00 -0000 [thread overview]
Message-ID: <20190306115712.GM3785@calimero.vinschen.de> (raw)
In-Reply-To: <1551866070633-0.post@n5.nabble.com>
[-- Attachment #1: Type: text/plain, Size: 1065 bytes --]
On Mar 6 02:54, jwang wrote:
> Good morning (UK time) All
>
> I downloaded the snapshots:
> https://cygwin.com/snapshots/x86_64/cygwin-20190304.tar.xz
>
> 1). tar -zvf cygwin-20190304.tzr.xz
tar: You must specify one of the '-Acdtrux', '--delete' or '--test-label' options
In the meantime you could just have installed 3.0.2 which is equivalent
to the latest snapshot.
> 2). cp -p /usr/bin/rsync usr/bin/
This doesn't make sense. Are you copying rsync into a local dir
with the extracted cygwin? Inside another Cygwin session?
Don't do that, you're bound to get into trouble.
> 3). usr/bin/rsync /tmp/test.log /tmp2/
Works fine for me
> 4). above failed with syntax error
> 5). strace usr/bin/rsync /tmp/test.log /tmp2/ showed similar error as
> before, i.e. named pipe issue et al
I mainly asked to try the latest snapshot to see the strace, because it
doesn't makes sense to inspect the strace of an old version. Please
attach the strace to your reply.
Thanks,
Corinna
--
Corinna Vinschen
Cygwin Maintainer
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-03-06 11:57 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-04 12:19 jwang
2019-03-04 12:36 ` Corinna Vinschen
2019-03-04 14:44 ` jwang
2019-03-05 9:46 ` jwang
2019-03-05 12:04 ` Corinna Vinschen
2019-03-05 13:16 ` jwang
2019-03-05 15:25 ` jwang
2019-03-06 10:00 ` jwang
2019-03-06 11:57 ` Corinna Vinschen [this message]
2019-03-06 12:05 ` jwang
2019-03-06 12:14 ` Corinna Vinschen
2019-03-06 14:00 ` jwang
2019-03-08 13:59 ` jwang
2019-03-08 14:18 ` Houder
2019-03-08 15:35 ` jwang
2019-03-08 20:59 ` Jerry Baker via cygwin
2019-03-09 1:23 ` jwang
2019-03-09 9:16 ` jwang
2019-03-11 15:02 ` jwang
2019-03-12 10:29 ` jwang
2019-03-16 8:36 ` jwang
2019-03-16 10:30 ` Houder
2019-03-16 10:49 ` jwang
2019-03-16 12:45 ` Houder
2019-03-16 13:13 ` jwang
2019-03-16 13:19 ` jwang
2019-03-16 13:26 ` jwang
2019-03-16 13:46 ` Houder
2019-03-16 14:18 ` jwang
2019-03-16 13:31 ` Houder
2019-03-17 6:45 ` Achim Gratz
2019-03-17 8:15 ` jwang
2019-03-17 9:07 ` Eliot Moss
2019-03-18 9:47 ` jwang
2019-04-02 8:45 ` jwang
2019-03-05 12:20 ` Andrey Repin
2019-03-05 13:15 ` jwang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190306115712.GM3785@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).