public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: gs-cygwin.com@gluelogic.com
To: Neil Aggarwal <neil@propfinancing.com>
Cc: cygwin <cygwin@cygwin.com>
Subject: Re: rsync gives me error 12
Date: Sun, 27 Mar 2022 01:08:00 -0400	[thread overview]
Message-ID: <Yj/xMAXorjeOgsIE@xps13> (raw)
In-Reply-To: <478bc24ecbb245e745f84837ab4a35d9@mail.gmail.com>

On Sat, Mar 26, 2022 at 11:49:18PM -0500, Neil Aggarwal wrote:
> The big stumper for me is that scp works.  What could cause rsync to act
> differently?

Likely answer: your server configuration, such as ssh config,
shell configuration, PATH, etc. which are a bit off-topic for
the cygwin list.

Manually ssh to the server and try to run `rsync -h`.

$ ssh -vvv user@server rsync -h

You can also get verbose ssh information from rsync using

$ rsync -e 'ssh -vvv' ...

You can also turn on verbose sshd logging
$ man sshd_config
See LogLevel and LogVerbose

  reply	other threads:[~2022-03-27  5:08 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-24  5:22 Neil Aggarwal
2022-03-25  9:45 ` Adam Dinwoodie
2022-03-25 13:25   ` Neil Aggarwal
2022-03-25 13:37     ` Adam Dinwoodie
2022-03-25 13:41       ` Neil Aggarwal
2022-03-25 17:14       ` Neil Aggarwal
2022-03-28 13:27         ` Andrey Repin
2022-03-28 14:06           ` Neil Aggarwal
2022-03-28 14:31           ` Neil Aggarwal
2022-03-25 17:36       ` Neil Aggarwal
2022-03-25 22:41         ` Wayne Davison
2022-03-26  5:01           ` Neil Aggarwal
2022-03-26 17:18             ` Wayne Davison
2022-03-27  4:49               ` Neil Aggarwal
2022-03-27  5:08                 ` gs-cygwin.com [this message]
2022-03-27 14:32                   ` Neil Aggarwal
2022-03-26 11:48         ` Adam Dinwoodie
2022-03-26 15:52           ` Neil Aggarwal

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=Yj/xMAXorjeOgsIE@xps13 \
    --to=gs-cygwin.com@gluelogic.com \
    --cc=cygwin@cygwin.com \
    --cc=neil@propfinancing.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).