DMARC-Filter: OpenDMARC Filter v1.4.2 delorie.com 53S8ZZ7U797203
DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org E154F3858D1E
Date: Mon, 28 Apr 2025 11:22:22 +0300
Message-ID: <785522855.20250428112222@yandex.ru>
To: "Agnihotri, Alok Kumar" <alokkumar.agnihotri@philips.com>,
        cygwin@cygwin.com
Subject: Re: Request for Assistance: Non-Functioning Commands in Cygwin
 Environment
In-Reply-To: <AM7P122MB01959A2A35168982969098ACEC812@AM7P122MB0195.EURP122.PROD.OUTLOOK.COM>
References: <AM7P122MB01959A2A35168982969098ACEC812@AM7P122MB0195.EURP122.PROD.OUTLOOK.COM>
MIME-Version: 1.0
Precedence: list
From: Andrey Repin via Cygwin <cygwin@cygwin.com>
Reply-To: cygwin@cygwin.com
Cc: Andrey Repin <anrdaemon@yandex.ru>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: cygwin-bounces~archive-cygwin=delorie.com@cygwin.com
Sender: "Cygwin" <cygwin-bounces~archive-cygwin=delorie.com@cygwin.com>

Greetings, Agnihotri, Alok Kumar!

> Dear Cygwin Technical Support Team,
> I hope this email finds you well.
> My name is Alok Agnihotri, and I am part of the Philips organization. We
> are utilizing Cygwin in our environment to execute SSH commands remotely on
> Windows-based machines, supporting various  activities critical to our operations.
> We are currently facing an issue where certain standard commands are not
> recognized or are failing to execute within the Cygwin environment.
> The list of affected commands includes:

>   * wmic
>   * perl
>   * egrep
>   * zip
>   * awk
>   * env
>   * head
>   * portqry
>   * reg query

egrep is obsolete (use `grep -E`), but it should work (see below).
To the other commands, awk, env, head - should work (reinstall and rebase
Cygwin if that's not the case). Same for zip and perl, if those are Cygwin
executables (make sure you actually have them installed).
In general, if you have silent crashes of Cygwin programs, it's often the
memory allocation issue, which could be caused by Cygwin installation when any
of the Cygwin processes running during package install. Setup could only
detect processes running when you start it, but if any of them are started and
still running when setup is actually installing packages, THAT could be a
problem. Another source of this issue is a badly behaving "antivirus"
injecting its libs at the wrong time in the wrong place. The third cause could
be forced ASLR. Cygwin's fork implementation is sensitive to address space
layout changes. Don't do that for Cygwin.

To the portqry, wmic and reg, IDK what is your issue. May be update Cygwin and
try again? There were changes in socket code regarding pipelining.


-- 
With best regards,
Andrey Repin
Monday, April 28, 2025 11:10:08

Sorry for my terrible english...


-- 
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple