public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Eliot Moss <moss@cs.umass.edu>
To: cygwin@cygwin.com
Subject: Re: Issue with delayed process start and effect on Windows 10
Date: Thu, 02 Feb 2017 23:27:00 -0000	[thread overview]
Message-ID: <d4f49819-0648-ed5a-80f1-b6b68657c1aa@cs.umass.edu> (raw)
In-Reply-To: <000501d27d99$0df69da0$29e3d8e0$@talk21.com>

On 2/2/2017 4:12 PM, Paul Kitchen wrote:
> Hello Barry,
>
> High Five to you!
>
> I do indeed have Rapport installed and it looks like it does not co-exist
> well with CYGWIN.
>
> I rebooted, stopped Rapport and then ran the script I have been trying to
> run for a day and it went through flawlessly at normal speed.
>
> It is very strange that 2 different applications that have nothing to do
> with each other can interfere with each other in this way.

Not so strange, in my experience with Cygwin.  Lots of security things
interpose themselves in ways that interfere.  In a way, that is what
they're designed to do - to intercept and block certain things.  But
sometimes they just slow down something they allow, something that
Cygwin does a lot, but that other Windows programs don't do so much,
so the purveyor perhaps never noticed the issue (or won't care because
the affected population is too small to be worth the effort).

Regards - Eliot Moss

--
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:[~2017-02-02 23:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-02 15:17 Paul Kitchen
2017-02-02 15:35 ` Andrey Repin
2017-02-02 16:51   ` Marco Atzeri
2017-02-02 20:40     ` Paul Kitchen
2017-02-03 22:13     ` Brian Inglis
2017-02-12 11:32       ` Corinna Vinschen
2017-02-02 20:04 ` bzs
2017-02-02 21:12   ` Paul Kitchen
2017-02-02 23:27     ` Eliot Moss [this message]
2017-02-03 22:46     ` 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=d4f49819-0648-ed5a-80f1-b6b68657c1aa@cs.umass.edu \
    --to=moss@cs.umass.edu \
    --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).