public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: getent doesn't work properly
Date: Fri, 18 Oct 2019 12:44:00 -0000	[thread overview]
Message-ID: <4b93af10-30a1-ad16-0c1f-7ccc30543500@SystematicSw.ab.ca> (raw)
In-Reply-To: <VI1P195MB076556407BF722B6618D58A8DE6D0@VI1P195MB0765.EURP195.PROD.OUTLOOK.COM>

On 2019-10-17 10:55, Jose Isaias Cabrera wrote:
>> Maayan Apelboim, on Thursday, October 17, 2019 09:02 AM, wrote:
>> It works fine for other users as much as I can tell.
>> The problem seems to be with one specific user.
>> myUser@dom1-job11 ~
>> $ getent passwd myUser
>> myUser:*:1049686:1049089:U-UK\myUser,S-1-5-21-892078619-2706518417-4190201681-1110:/home/myUser:/bin/bash
>> myUser@dom1-job11 ~
>> $ getent passwd user1
> Long time ago, I had a problem like that, and I think it was the last line on the passwd file.  But, I don't think it's the case with yours.

What is enumerated from SAM/AD by getent is controlled by /etc/nsswitch.conf
entry db_enum which defaults to:

# db_enum:  cache builtin

I changed my SAM, non-AD, non-domain system to:

db_enum:    cache local builtin

Please read the rest of the info about db_enum in /etc/nsswitch.conf and set up
your system accordingly.

If you are in a domain with AD, it will be worth your while to configure and run
cygserver service, under cygrunsrv, to cache your AD entries.
Even if you are on a SAM, non-AD, non-domain system, if you run a lot of Cygwin
processes, or use cron a lot, it will be worth your while to configure and run
cygserver service, under cygrunsrv, to cache your SAM and process entries.

If you run a lot of processes, it may be worth maximizing some entries in
/etc/cygserver.conf:

# kern.srv.cleanup_threads: No. of cygserver threads used for cleanup tasks.
# Default: 2, Min: 1, Max: 16, command line option -c, --cleanup-threads
#kern.srv.cleanup_threads 2
kern.srv.cleanup_threads 16

# kern.srv.request_threads: No. of cygserver threads used to serve
#                           application requests.
# Default: 10, Min: 1, Max: 310, command line option -r, --request-threads
#kern.srv.request_threads 10
kern.srv.request_threads 310

# kern.srv.process_cache_size: No. of concurrent processes which can be handled
#                              by Cygserver concurrently.
# Default: 62, Min: 1, Max: 310, command line option -p, --process-cache
#kern.srv.process_cache_size 62
kern.srv.process_cache_size 310

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.

--
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

  reply	other threads:[~2019-10-18 12:44 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 [this message]
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
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=4b93af10-30a1-ad16-0c1f-7ccc30543500@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --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).