From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: cygwin@cygwin.com
Subject: Re: Possible cygwin scp bug
Date: Sat, 16 Jul 2022 22:35:05 +0900 [thread overview]
Message-ID: <20220716223505.3c7ded42af1335a14e8d4f19@nifty.ne.jp> (raw)
In-Reply-To: <CAOmkcGvZOe3kKRTaSKbP6FH8Dn=SuVUrfP1q9gUkp6P_dvaWUQ@mail.gmail.com>
On Sat, 16 Jul 2022 09:19:35 -0400
"Knight, Dave" wrote:
> I am running cygwin virtualbox running a WinDev2206Eval "appliance" (.ova
> from microsoft). Everything else I've tested so far in cygwin runs as
> expected except scp when the <source> file path is an absolute path, e.g.
> /tmp/foo. Scp <source> references to that file using a relative path, e.g.
> ../../tmp/foo, work fine. For example:
>
> $ ls > /tmp/foo # create a /tmp/file
> $ ls -l /tmp/foo
> $ scp /tmp/foo bcserver:foobar # fails with /tmp/foo "file not found"
> $ pwd # (CWD is /Users/dmk)
> $ scp ../../tmp/foo bcserver:foobar # this works
> $ cd /tmp
> $ scp foo bcserver:foobar # this also works
>
> Please see the attached (script) log file scp.log for the actual results
> using these commands.
> See also the attached cygcheck.out file.
>
> Note that:
>
> 1 - absolute paths work OK for an scp <destination> pathname
>
> 2 - the "scp /tmp/foo bcserver:foobar" command works OK in win11's
> PowerShell
>
> 3 - the scp target host (bcserver) is a FreeBSD 12 OS running in a
> TrueNAS "jail".
You do not seem to install cygwin scp (openssh package), do you?
--
Takashi Yano <takashi.yano@nifty.ne.jp>
prev parent reply other threads:[~2022-07-16 13:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-16 13:19 Knight, Dave
2022-07-16 13:35 ` Takashi Yano [this message]
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=20220716223505.3c7ded42af1335a14e8d4f19@nifty.ne.jp \
--to=takashi.yano@nifty.ne.jp \
--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).