From: Andrey Repin <anrdaemon@yandex.ru>
To: Maayan Apelboim <Maayan.Apelboim@clarizen.com>, cygwin@cygwin.com
Subject: Re: getent doesn't work properly
Date: Mon, 28 Oct 2019 17:35:00 -0000 [thread overview]
Message-ID: <1185423087.20191028202914@yandex.ru> (raw)
In-Reply-To: <AM4PR07MB34735BAE3859C6770382E2B995680@AM4PR07MB3473.eurprd07.prod.outlook.com>
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
next prev parent reply other threads:[~2019-10-28 17:35 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-17 9:02 Maayan Apelboim
2019-10-17 12:23 ` Jose Isaias Cabrera
2019-10-17 13:02 ` Maayan Apelboim
2019-10-17 16:55 ` Jose Isaias Cabrera
2019-10-18 12:44 ` Brian Inglis
2019-10-18 10:52 ` Corinna Vinschen
2019-10-23 11:17 ` Maayan Apelboim
2019-10-23 11:42 ` Corinna Vinschen
2019-10-23 13:28 ` Brian Inglis
2019-10-23 13:33 ` Maayan Apelboim
2019-10-24 14:06 ` Corinna Vinschen
2019-10-28 8:56 ` Maayan Apelboim
2019-11-13 12:04 ` Maayan Apelboim
2019-11-13 12:08 ` Maayan Apelboim
2019-10-18 11:05 ` Andrey Repin
2019-10-22 8:22 ` Maayan Apelboim
2019-10-28 17:35 ` Andrey Repin [this message]
2019-10-29 0:03 ` Brian Inglis
2019-11-13 15:18 ` Maayan Apelboim
2019-11-25 13:29 ` Maayan Apelboim
2019-11-25 15:24 ` Maayan Apelboim
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=1185423087.20191028202914@yandex.ru \
--to=anrdaemon@yandex.ru \
--cc=Maayan.Apelboim@clarizen.com \
--cc=cygwin@cygwin.com \
/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).