DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:reply-to:message-id:to:subject
	:in-reply-to:references:mime-version:content-type
	:content-transfer-encoding; q=dns; s=default; b=sQ6a+FtYP76TdUDE
	gc4oMW9VTf64RFZ+30hiWfZcz3D761PBKG73mo85XJd3mA2HLH82AoaQrVBF+RCo
	8rdQtPk0BCMQzyLHNpfLtyzLt5acVKBqOoAqYPR/0SuUjksiJ+0g+GNJWlWsj9kC
	zrlN/xmR9nc4w5Qg6fHK5tLq4Ow=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Fri, 28 Feb 2014 03:12:19 +0400
From: Andrey Repin <anrdaemon@yandex.ru>
Reply-To: cygwin@cygwin.com
Message-ID: <765945729.20140228031219@yandex.ru>
To: Corinna Vinschen <cygwin@cygwin.com>
Subject: Re: Testers needed:  New passwd/group handling in Cygwin
In-Reply-To: <20140227134632.GG2246@calimero.vinschen.de>
References: <20140225200414.GA4238@calimero.vinschen.de> <87y50zaqjb.fsf@Rainer.invalid> <20140225215423.GA6065@calimero.vinschen.de> <loom.20140226T085959-119@post.gmane.org> <20140226100209.GR2246@calimero.vinschen.de> <20140226135222.GW2246@calimero.vinschen.de> <loom.20140227T095414-414@post.gmane.org> <loom.20140227T100638-8@post.gmane.org> <20140227094951.GD2246@calimero.vinschen.de> <loom.20140227T134714-188@post.gmane.org> <20140227134632.GG2246@calimero.vinschen.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Greetings, Corinna Vinschen!

>> > 1 second?  That sounds still a bit slow.  Considering that I'm now
>> > member of 414 groups, and you are member of 440 groups, the extra number
>> > of groups cannot account for that.
>> >
>> >  This sounds surprisingly as if the
>> > names of some of your groups are not cached on your machine.  Or
>> > something.  Or is this a rather slow machine?!?
>>  
>> It's not a slow machine by any means, but it certainly gets its fair share
>> of security policies, so it may have something to do with that.  I don't know.
>> 
>> > Still, it seems like the right thing to do to drop the group name
>> > configuration stuff entirely.
>> 
>> Yes (unless you'd want to make it configurable like the getpwent stuff).

> Nah, not really.  As I said, I'm questioning some of the old functionality
> anyway, and the less we have to ask AD the better for us.

> I applied my patch which removes this group name change facility from AD
> and uploaded a new snapshot to http://cygwin.com/snapshots/.

> While we're at it, I just had this weird idea.

> What if, as soon as the first Cygwin process in a process tree starts,
> this process not only caches the primary group info, but also caches all
> supplementary groups from the user's token?  This would slow down
> startup of the first process slightly, but it would speed up any
> subsequent request for group information of a group in the user's token.
> An `id' call would be almost instant, and `ls' calls would probably be
> faster as well.

Umhm. I'd have to see, how slightly. Because my primary use of Cygwin tools
does not expect to have a parent Cygwin process. (I.e. diff'ing between
file manager panels.)

> As always, there's a trade-off: Users running cygwin processes from CMD
> a lot would encounter a slowdown.

> What do you think, guys?

Needs some tests. I would certainly appreciate faster initial startups, but if
the delay is manageable, I can cope with more long-term friendly approach.
I've got entangled in current work and lost track of snapshots for now.
If there's some DEF's in library, that I can toggle and rebuild it with certain
features enabled and disable for local test, I'd be glad to have a round at it
over weekend.


--
WBR,
Andrey Repin (anrdaemon@yandex.ru) 28.02.2014, <03:06>

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