public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Ben Altman <benalt@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Extreme Slowness of cygwin commands [SOLVED?]
Date: Thu, 01 Sep 2016 15:57:00 -0000	[thread overview]
Message-ID: <963747c6-a86b-fa30-1a03-b3a033c4588c@gmail.com> (raw)
In-Reply-To: <22468.35759.296399.313474@gargle.gargle.HOWL>

On 8/29/2016 3:23 PM, bzs@theworld.com wrote:
> On August 29, 2016 at 01:18 benalt@gmail.com (Ben Altman) wrote:
>   >
>   > This comes a while later but I was wrong and you were right.
>   >
>
> Glad to be of service.

As a follow up, I contacted Trusteer about the issue and did some basic 
troubleshooting and it turns out that Rapport Cerberus, one of Rapport's 
Anti-malware protection mechanisms, was the issue. Renaming all the sys 
files in 
C:\ProgramData\Trusteer\Rapport\store\exts\RapportCerberus\baseline and 
rebooting solved the problem. In the meanwhile, they said they expect 
the problem to be resolved in a future release of Rapport.

Ben

--
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

  reply	other threads:[~2016-09-01 15:57 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-27  6:25 bzs
2016-05-27  7:42 ` Ben Altman
2016-05-28 10:05   ` bzs
2016-05-28 12:10     ` Ben Altman
2016-08-29 12:06       ` Ben Altman
2016-08-30  7:34         ` bzs
2016-09-01 15:57           ` Ben Altman [this message]
2016-09-01 17:19             ` bzs
2016-09-01 17:52               ` Erik Soderquist
2016-09-01 18:19                 ` bzs
2016-09-01 18:28                   ` Erik Soderquist
2016-09-01 18:37                   ` Alan Dobkin
2016-09-01 18:59                   ` Brian Inglis

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=963747c6-a86b-fa30-1a03-b3a033c4588c@gmail.com \
    --to=benalt@gmail.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).