public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Antonio Petrelli <antonio.petrelli@gmail.com>
To: Ken Brown <kbrown@cornell.edu>
Cc: The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: cygpath not doing anything on a fresh install
Date: Tue, 8 Feb 2022 17:04:27 +0100	[thread overview]
Message-ID: <CAHTRnezeXgEyeSWdkEJxUeDjDvD7zpvfaxRSR+OPD2u9w5R9Dg@mail.gmail.com> (raw)
In-Reply-To: <82bdb54f-7ebb-58be-7467-6e107a57244a@cornell.edu>

Il giorno mar 8 feb 2022 alle ore 15:57 Ken Brown <kbrown@cornell.edu> ha
scritto:

> On 2/8/2022 9:37 AM, Antonio Petrelli wrote:
> > Il giorno mar 8 feb 2022 alle ore 15:30 marco atzeri <
> marco.atzeri@gmail.com>
> > ha scritto:
> >> check if strace give some hints
> >>
> >>    strace -o /tmp/strace.txt /usr/bin/cygpath --help
> >>
> >
> > The result is here:
> > https://pastebin.com/n56RTAiu
>
> This looks suspicious:
>
> Process 2480 loaded C:\Program Files\SentinelOne\Sentinel Agent
> 21.7.4.1043\InProcessClient64.dll at 00007ffb7c940000
>
> I suspect that SentinelOne is interfering with Cygwin (see
> https://cygwin.com/faq/faq.html#faq.using.bloda).  Can you disable it or
> at
> least exclude the Cygwin directory from whatever it does?
>

No I can't, at least not immediately, it's controlled by the corporate.
I think that SentinelOne can be safely put in the list of interfering
software :-(

Thanks anyway
Antonio

  reply	other threads:[~2022-02-08 16:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-08 12:06 Antonio Petrelli
2022-02-08 12:28 ` Andrey Repin
2022-02-08 14:06   ` Antonio Petrelli
2022-02-08 14:19     ` marco atzeri
2022-02-08 14:23       ` Antonio Petrelli
2022-02-08 14:30         ` marco atzeri
2022-02-08 14:37           ` Antonio Petrelli
2022-02-08 14:57             ` Ken Brown
2022-02-08 16:04               ` Antonio Petrelli [this message]
2022-02-08 18:02                 ` Marco Atzeri

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=CAHTRnezeXgEyeSWdkEJxUeDjDvD7zpvfaxRSR+OPD2u9w5R9Dg@mail.gmail.com \
    --to=antonio.petrelli@gmail.com \
    --cc=cygwin@cygwin.com \
    --cc=kbrown@cornell.edu \
    /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).