public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: commands spends time in cygheap_user
Date: Mon, 17 Aug 2015 20:55:00 -0000	[thread overview]
Message-ID: <20150817205517.GI17917@calimero.vinschen.de> (raw)
In-Reply-To: <20150817081337.GF25127@calimero.vinschen.de>

[-- Attachment #1: Type: text/plain, Size: 1591 bytes --]

On Aug 17 10:13, Corinna Vinschen wrote:
> On Aug 17 10:07, Corinna Vinschen wrote:
> > On Aug 16 05:35, mku wrote:
> > > I changed cygwin1.dll to Version 2.2.1 and got the results shown in the
> > > attached log file (
> > > cygwin-time-lag.txt
> > > <http://cygwin.1069669.n5.nabble.com/file/n120553/cygwin-time-lag.txt>  ).
> > > I'm sorry to say that the problem has not disappeared with that patch.
> > 
> > 
> > Too bad, I thought skipping the SID<->uid mapping per RFC 2307 is the
> > culprit.
> 
> s/is the culprit/fixes the problem.
> 
> > 
> > Are you sure your /etc/nsswitch.conf is set to
> > 
> >   passwd: files
> >   group: files
> > 
> > Can you print it out, please?
> > 
> > I'll try to reproduce this again in the next few days.

I managed to reproduce the issue and I think I found the actual problem
here.  When trying to create the supplementary group list of the current
user, Cygwin called LookupAccountSids indiscriminately.  If you don't
have access to your AD, this call is bound to take some time, 5 to 10
secs in my testing.

I changed the code so that when "group: db" is set in /etc/nsswitch.conf
it will only utilize /etc/group to fetch group information.

I uploaded a new developer snapshot containing this patch to
https://cygwin.com/snapshots/  Please give it a try.  For testing, just
replace your current DLL with the snapshot DLL temporarily.


Thanks,
Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

  parent reply	other threads:[~2015-08-17 20:55 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-17  6:26 pen
2015-08-07  8:48 ` mku
2015-08-07  9:06   ` Corinna Vinschen
2015-08-07 19:51     ` mku
2015-08-10  8:40       ` Corinna Vinschen
2015-08-10 12:00         ` mku
2015-08-10 16:01           ` Corinna Vinschen
2015-08-12 11:59             ` mku
2015-08-12 14:47               ` Corinna Vinschen
2015-08-14 13:49                 ` mku
2015-08-14 15:48                   ` Corinna Vinschen
2015-08-14 20:20                     ` Corinna Vinschen
2015-08-15 11:54                       ` Corinna Vinschen
2015-08-16 12:50                         ` mku
2015-08-17  8:07                           ` Corinna Vinschen
2015-08-17  8:13                             ` Corinna Vinschen
2015-08-17 10:10                               ` mku
2015-08-17 20:55                               ` Corinna Vinschen [this message]
2015-08-17 21:04                                 ` Corinna Vinschen
2015-08-18  8:17                                   ` mku
2015-08-18  8:30                                     ` Corinna Vinschen
2015-08-14 13:49             ` Corinna Vinschen

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=20150817205517.GI17917@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.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).