DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:to:from:subject:date:message-id:references
	:mime-version:content-type:content-transfer-encoding
	:in-reply-to; q=dns; s=default; b=nElyMLdBDDUpCmiJwTzDfcGdvQHiRW
	P3YbhJb3FLGk1PC91HQtp2K71uh/z+GwUE5UnNU+gez9/hR7BOBIkiBzfdfVMCmv
	tAtrsGUW58R5OgZHc25SDkk9WiY/35BEY+Gx2+0VpertXlizgMY9MiL9k+v3eg8R
	z6K0zZDxzcKBU=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
To: cygwin@cygwin.com
From: Achim Gratz <Stromeko@Nexgo.DE>
Subject: Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 2.3.0-0.4
Date: Tue, 27 Oct 2015 10:53:44 +0100
Lines: 42
Message-ID: <n0nhja$1ji$1@ger.gmane.org>
References: <announce.20151022162227.GC5319@calimero.vinschen.de> <loom.20151023T153449-500@post.gmane.org> <20151026100756.GC31990@calimero.vinschen.de> <562E4ED0.7020907@Nexgo.DE> <20151027092722.GN5319@calimero.vinschen.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
In-Reply-To: <20151027092722.GN5319@calimero.vinschen.de>

Am 27.10.2015 um 10:27 schrieb Corinna Vinschen:
>> That test is almost as bad as it can ever get.  Given that enumerating all
>> AD accouts with mkpasswd takes about 2 hours and I'm doing something very
>> similar here, I'm not even surprised.  I was more surprised to see the
>> server go so fast, but my guess is that it can use jumbo frames to talk to
>> the AD.
>
> Ok, so you don't seem to think this is a major drawback.

I didn't say I would not like to see it run faster.  But considering the 
alternatives, working correctly all the times at the current speed seems 
to cover my more typical uses a lot better.

> No worries.  I'm mulling over the idea to release 2.3.0 this week
> without the new ACL handling code to get the latest fixes out of the
> door first and push this stuff into a 2.4.0 release in November.

As long as you keep reminding us which snapshot has the new ACL handling 
code, that is OK with me.  I will want to push out the snapshot in a 
week or two and remove some of my workarounds for ACL corrections and/or 
noacl mounted directories in order to see if these things are working 
now for real.

>>> Given the above result, I'm wondering if we can afford using AuthZ at
>>> all.  OTOH I don't see any other way to get the correct POSIX permissions
>> >from a non-Cygwin ACL :(
>>
>> If you really want fast but incorrect there's always the "noacl" mount
>> option.
>
> Right.  OTOH, maybe we could enhance the "acl" mount option?
>
> "acl" -> "quickacl" -> "noacl"?

Let's worry about that middle ground scenario when the ACL code has 
proven itself.  The danger here is that the edge cases that will make 
problems are not easy to spot before you run into them

-- 
Achim.

(on the road :-)


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