HI Andrey Thanks for your quick response .
Can you please suggest which Cygwin version should be use so that we dont face issue with these commands . Thanks Alok Agnihotri ________________________________ From: Andrey Repin <anrdae...@yandex.ru> Sent: Monday, April 28, 2025 1:52 PM To: Agnihotri, Alok Kumar <alokkumar.agniho...@philips.com>; cygwin@cygwin.com <cygwin@cygwin.com> Subject: Re: Request for Assistance: Non-Functioning Commands in Cygwin Environment [You don't often get email from anrdae...@yandex.ru. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ] Caution: This e-mail originated from outside of Philips, be careful for phishing. 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... ________________________________ The information contained in this message may be confidential and legally protected under applicable law. The message is intended solely for the addressee(s). If you are not the intended recipient, you are hereby notified that any use, forwarding, dissemination, or reproduction of this message is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender by return e-mail and destroy all copies of the original message. -- 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
