public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: ASSI <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: "/usr/bin/tar.exe" hangs, Windows 10, CYGWIN_NT-10.0 3.0.7(0.338/5/3) 2019-04-30 18:08 x86_64
Date: Sat, 16 Nov 2019 13:39:00 -0000	[thread overview]
Message-ID: <874kz4aygm.fsf@Rainer.invalid> (raw)
In-Reply-To: <CAFWoy7EQJ8HP6Bt4qwdMebh0Vrq6=FxCCQQPo_Uut4+LoWmgEQ@mail.gmail.com>	(Keith Christian's message of "Fri, 15 Nov 2019 15:06:56 -0700")

Keith Christian writes:
> This is a corporate PC so little chance of doing any uninstalls or
> modification.  At least I know why now, and you've given me some ideas
> about troublesome DLL's.

Been there, done that.  Usually Symantec Endpoint Protection does come
with a support contract and Symantec support definitely knows about
Cygwin even when your IT folks don't.  So open ticket, support request
or whatever they call it with your IT and insist they escalate to
Symantec if they can't solve your problem (e.g. by excluding the Cygwin
install directory from heuristic checks).  The problem may return after
some updates or whenever someone feels that your company devices need
"extra" protection.  Sometimes it helps to do a full scan on the Cygwin
install directory, as some of the more problematic heuristics are
skipped when the scanner has seen and whitelisted a file before.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptation for Waldorf microQ V2.22R2:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada

--
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:[~2019-11-16 10:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-15 14:40 Keith Christian
2019-11-15 15:13 ` Ken Brown
2019-11-15 15:30   ` Keith Christian
2019-11-15 17:34     ` Ken Brown
2019-11-15 18:39     ` Brian Inglis
2019-11-15 22:25       ` Keith Christian
2019-11-16 13:39         ` ASSI [this message]
2019-11-16 18:40           ` 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=874kz4aygm.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --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).