Greetings, Maayan Apelboim! >> You aren't running Cygwin Cygserver and I don't see your nsswitch setup. > >> P.S. >> Also, please no top-posting in this list.
> Sorry for top posting, my bad :) > I have the default nsswitch - This is my configuration: > # /etc/nsswitch.conf > # > # This file is read once by the first process in a Cygwin process tree. > # To pick up changes, restart all Cygwin processes. For a description > # see https://cygwin.com/cygwin-ug-net/ntsec.html#ntsec-mapping-nsswitch > # > # Defaults: > # passwd: files db > # group: files db > # db_enum: cache builtin > # db_home: /home/%U > # db_shell: /bin/bash > # db_gecos: <empty> That should be sufficient for most use cases. > Why do I need cygserver? You don't exactly NEED cygserver. But if you have 1. Domain (or even multi-domain) environment. 2. and/or remote/slow/flaky connection to the domain server. cygserver may provide a smoother experience as it caches some information related to names resolution. > I don't have it on any other server and everything works fine. > I actually have this problem only in one env - the rest works as expected. > All servers are installed the same, but for some reason this problem > persists only in one env / domain, and one server specifically has this > problem more than others (even after reinstallation). -- With best regards, Andrey Repin Monday, October 28, 2019 20:25:38 Sorry for my terrible english... -- 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