From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12408 invoked by alias); 14 Apr 2015 16:21:56 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 12385 invoked by uid 89); 14 Apr 2015 16:21:55 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-0.4 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY,SPAM_BODY1 autolearn=no version=3.3.2 X-HELO: calimero.vinschen.de Received: from aquarius.hirmke.de (HELO calimero.vinschen.de) (217.91.18.234) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 14 Apr 2015 16:21:54 +0000 Received: by calimero.vinschen.de (Postfix, from userid 500) id 05B90A807D2; Tue, 14 Apr 2015 18:21:52 +0200 (CEST) Date: Tue, 14 Apr 2015 16:21:00 -0000 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: Making Cygwin More Tolerant of Orphaned SIDs? Message-ID: <20150414162151.GP7343@calimero.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <20150414080044.GB7343@calimero.vinschen.de> <20150414092313.GE7343@calimero.vinschen.de> <20150414145323.GH7343@calimero.vinschen.de> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="FvF9dqTwB4R3n80B" Content-Disposition: inline In-Reply-To: <20150414145323.GH7343@calimero.vinschen.de> User-Agent: Mutt/1.5.23 (2014-03-12) X-SW-Source: 2015-04/txt/msg00315.txt.bz2 --FvF9dqTwB4R3n80B Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Content-length: 2341 On Apr 14 16:53, Corinna Vinschen wrote: > On Apr 14 07:24, Bryan Berns wrote: > > On Tue, Apr 14, 2015 at 4:00 AM, Corinna Vinschen > > > > > > The problem is that Cygwin, or any other tool trying to resolve SIDs > > > doesn't know a SID won't resolve before it tried. And then it's an > > > OS function which takes its time. It's like checking for network > > > machines providing shares. Sometimes this test takes ages, but in > > > this case, fortunately, you see that it takes ages in Explorer as > > > well. > > > > > > As for ACLs, you can alleviate the problem somewhat by running cygser= ver > > > on the machine, which allows to cache SIDs for all processes. So only > > > the first process trying the SID will take time, followup processes w= ill > > > get the cached results from cygserver. > > > > > > Other than that, except for ignoring ACLs entirely (noacl) I have > > > no idea how to solve this problem differently. > >=20 > > Yes, I understand there's nothing Cygwin can do beforehand -- that > > means sense. I guess what I'm saying is that Cygwin doesn't appear to > > be caching SIDs in certain scenarios. > >=20 > > For example, I create a whole bunch of files (like 5000), I use > > icacls to append a new ACE. Then I do a 'time ls -l > > /cygdrive/c/somedir/*'. Takes four seconds. In the same Cygwin > > session, I remove the local group (net localgroup testgroup /delete). > > I do the same 'time ls -l /cygdrive/c/somedir/*'. Takes 20 seconds. > > Subsequent runs in the also take 20 seconds. Since I'm able to > > continue to see the slowdown in the same session, cygserver wouldn't > > help right? > >=20 > > Is the above expected? >=20 > Yes. Without cygserver, caching only works from parent to child process. > One run of ls can't cache data for a parallel run of ls in trhe same > session. As, btw., explained in the documentation: >=20 > https://cygwin.com/cygwin-ug-net/ntsec.html ...and if my reply wasn't clear enough: Cygserver will help in this scenario as outlined in the documentation. It caches the account information system-wide, so the stuff the first ls cached is available for the next ls. Or the next shell session. Corinna --=20 Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat --FvF9dqTwB4R3n80B Content-Type: application/pgp-signature Content-length: 819 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBAgAGBQJVLT6fAAoJEPU2Bp2uRE+gyxgP/RonFy77jNmJ64n1wDzupTzU mUD3sdGFhaY+xmnAUrtbr6HFN/1lbfHmyxsa+I/ofnWEvCGv1VgRfYKG6F5Qs5Nm RVSOdeOw67eSHAXSvu2lafZVUTRCxDK3Th9/hXcjTIS/hGoqPktUkmz2dYtg9yfl z/0jYXwoh0VSOWSZY0lmq0Yd7bgnXQXBxNV/KQ6+vQuE3XP1goocfsQMYLeBbXRu fD303ggG9uSJ7Ss9mC379CGtQGM+aTWUj4pjTUUEJ9vLaC1j+A2aIb5QcAEDf33Z XiroxyWW9GEN3PgdU4cImXUnEPaqAaVapFNpVxLECLlSlCFX99Uv0l02T9RASln1 bbmWsHmn+YCqzLtuDdOvgJOleNTjWfAXQo10fZXSnnXc1XRo0UlgiirZK7bwI3cZ hmDq6H3NxfCm5OzXaUEPXQTLwnoE7SoShtmDp9Euv6GFKDqTWgBFghEaKhaONveM Ha+On+DmwUsvdrkiDp6eS52KJ/UFA3vPk1Y/icSgCVagx/KMczn+riyZddR9Ik4v p9m96p2Ygcvr0O6S6bk5anBKq1UtEimN5coVLoQxXMbP5FeawWY+bwV2WNsfOx7V aPDCpcCe15IPDkuUwnUWopxqAe2LQXaYMs07HHMQPfqKTv8wmr+tW159K0prFMch WGDLI6wptl6Zgqvq7y20 =nKBD -----END PGP SIGNATURE----- --FvF9dqTwB4R3n80B--