Greetings, Agnihotri, Alok Kumar! This list uses a bottom-posting for easier navigation of reply history.
>>> 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. > Thanks for your quick response . > Can you please suggest which Cygwin version should be use so that we dont > face issue with these commands . There's no such thing as "Cygwin version" aside from the Cygwin1 DLL itself. Cygwin as an application is a package management system that helps you install the packages you want in an easy way. As I outlined above, the problem could come from more than one source. First thing should be a clean upgrade in either way, making sure no suddenly spawned Cygwin processes could interfere with it. Then (if that didn't help) `rebase-trigger full` with subsequent run of setup.exe (see docs for details). After that, it's likely an external issue (AV/OS interfering), and there's steps and hints to diagnose and mitigate it in the list archives. -- With best regards, Andrey Repin Tuesday, April 29, 2025 12:52:45 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
