public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Andrey Repin <anrdaemon@yandex.ru>
To: "Morten Kjærulff" <mortenkjarulff@gmail.com>, cygwin@cygwin.com
Subject: Re: sshfs or alike
Date: Fri, 8 May 2020 23:24:39 +0300	[thread overview]
Message-ID: <803666546.20200508232439@yandex.ru> (raw)
In-Reply-To: <CA+7cx1rv0KjcCmZ5Ctw-3q_9K8vcpMruJsfHmNoUnFBQi+XP_w@mail.gmail.com>

Greetings, Morten Kjærulff!

>> > As I understand, you can get sshfs to work with cygwin, but you have
>> > to install some non-cygwin tools also.
>>
>> > Can I get sshfs or something like that with only cygwin tools?
>>
>> Adding to the already mentioned points, I should warn you that SSHFS is
>> EXTREMELY SLOW. By design.
>> Enumerating significant amount of files could take minutes. If you can use any
>> other tools (like, OpenVPN + CIFS), it will be hundred if not thousand times
>> faster.

> Would this be cygwin only?

No. Recently I've tried both sshfs/wfsp outlined earlier in the thread and two
native sshfs solutions on the same target system, all exhibit same behavior.

Running "git status" on a project directory takes:

- locally on the host: up to 10s;
- over CIFS share: up to 30s;
- over SMBFS share: up to half an hour(!).

> My server is a z/OS mainframe, where we just installed sshd. Anyone
> have good tips?

You should first think about your needs and use cases. Do you actually need
filesystem features? Or all you need is the ability to copy files to/from the
server?

For SSH, rsync and git both coming to mind.


-- 
With best regards,
Andrey Repin
Friday, May 8, 2020 23:04:16

Sorry for my terrible english...

      parent reply	other threads:[~2020-05-08 20:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-06 18:14 Morten Kjærulff
2020-05-06 19:22 ` Marco Atzeri
2020-05-06 19:33 ` Brian Inglis
2020-05-08  9:46 ` Andrey Repin
2020-05-08 14:29   ` Morten Kjærulff
2020-05-08 15:31     ` Maarten Hoes
2020-05-08 17:17     ` Brian Inglis
2020-05-08 20:24     ` Andrey Repin [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=803666546.20200508232439@yandex.ru \
    --to=anrdaemon@yandex.ru \
    --cc=cygwin@cygwin.com \
    --cc=mortenkjarulff@gmail.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).