From: ncoif <ncoif@gmx.com>
To: cygwin@cygwin.com
Subject: Re: Slowness with cygwin from behind a VPN
Date: Tue, 13 Sep 2016 14:50:00 -0000 [thread overview]
Message-ID: <676d9d94-02dc-c874-12c7-398c23067e24@gmx.com> (raw)
In-Reply-To: <c10e1a72-9d49-930f-16ef-d16afa3ded18@gmx.com>
Thanks a lot Marko, this link works fine for me!!
probably the VPN is adding delays in recovering user or group data.
You can try if running cygserver improve the performance:
https://cygwin.com/cygwin-ug-net/ntsec.html#ntsec-mapping-caching
On 12/09/2016 15:42, ncoif wrote:
> Hi everyone,
>
> I've noticed a problem with a specific command on cygwin, but only
> when executed behind a VPN. I would like to know how to find more
> information about this problem, and/or how/where to report this
> potential bug.
>
> The following command is taking a lot of time behind a VPN (works fast
> without the VPN):
> cmd.exe /X /C "git --version"
> Running git --version works equally fast in both cases, so I would
> guess there is a problem in cmd.exe/cygwin, but I'm not sure. Any
> suggestion on how to gather more information about the network is
> welcome.
>
> My cygwin version:
> $ uname -r
> 2.6.0(0.304/5/3)
>
> My cmd.exe version:
> OS Name: Microsoft Windows 7 Enterprise
> OS Version: 6.1.7601 Service Pack 1 Build 7601
>
> My git version: 2.8.3
>
> Sincerely,
> ncoif
>
> PS: This is my first time on this mailing list, so please apologize
> for my mistakes.
--
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
prev parent reply other threads:[~2016-09-13 10:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-12 14:41 ncoif
2016-09-12 20:43 ` Marco Atzeri
2016-09-13 14:50 ` ncoif [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=676d9d94-02dc-c874-12c7-398c23067e24@gmx.com \
--to=ncoif@gmx.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).