From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30723 invoked by alias); 1 Sep 2014 11:57:05 -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 30712 invoked by uid 89); 1 Sep 2014 11:57:04 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-5.9 required=5.0 tests=AWL,BAYES_00 autolearn=ham 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; Mon, 01 Sep 2014 11:57:03 +0000 Received: by calimero.vinschen.de (Postfix, from userid 500) id 841608E1402; Mon, 1 Sep 2014 13:57:01 +0200 (CEST) Date: Mon, 01 Sep 2014 11:57:00 -0000 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: (call-process ...) hangs in emacs Message-ID: <20140901115701.GD2644@calimero.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <87wq9v9j2y.fsf@Rainer.invalid> <53FD0662.5050208@cornell.edu> <20140827084245.GD20700@calimero.vinschen.de> <53FDD4A8.5050401@cornell.edu> <20140828095524.GO20700@calimero.vinschen.de> <20140828131832.GT20700@calimero.vinschen.de> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="GyRA7555PLgSTuth" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) X-SW-Source: 2014-09/txt/msg00003.txt.bz2 --GyRA7555PLgSTuth Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Content-length: 1193 On Aug 29 09:58, Achim Gratz wrote: > Achim Gratz NexGo.DE> writes: > > > Please test. > >=20 > > This fixes the "read-only" problem in Emacs (so that hunch was correct)= .=20 > > Perl still doesn't play, but I think the 5.18 version should get it cor= rect. > > Will need to switch a test installation over for that, though. >=20 > With that snapshot in place, ssh suddenly recognized that my private key > file was more readable than it liked it to be, so it looks that it's using > the same general strategy of dealing with ACL as Emacs. I'm starting to > like this patch very much... :-) Over the weekend it occured to me that the acl(2) function created ACLs which not aligned well with the ACLs created by open(2),chmod(2), etc. Yesterday I fixed the acl(2) function to create ACLs the same way as=20 the other functions, especially in terms of the owner and group entries and the SE_DACL_PROTECTED flag. The changes are in the latest snapshot from https://cygwin.com/snapshots/ Please give them a try. Thanks, Corinna --=20 Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat --GyRA7555PLgSTuth Content-Type: application/pgp-signature Content-length: 819 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJUBF8NAAoJEPU2Bp2uRE+g5+QP/jpXlAzEI1ocPwZ0twINS6V7 LvdSgnBHktR9Ye6NXJGVqHFEOrzs8xl/EZ42XswZBk3xFllDqrMa+OtnkWXhZRDW MGLzUiw/5EsBzcqiPVHvs1ip4ZRiGl2e33CCoo8ihU+JxfxNfbGRnBj8OzYKlD2q I8ml95PqdRbHZXWeD372slr6agsmOtr86i+JOO6gqzutJZYcVDyemp/Evy92mPt9 oCPAwXSTSskYuSmtTVQOB20IYciQbfv0nJ6hRw5pRkIxj++eZTEK+PSQ/xKU8Bn7 gl+i+S4dgOv2MlutQ1OG9QVgbNgZ9MKaDlaJU0qBmPMIIFezVxHPpoyioGtmrA0u 6+ubkU5uAYgxZL2TAGHUVX2zWzyCa88JenH64jtZoPp0MtRzAZzKcq8TIC3Z6LLH CzcmkCBZWDm0mAYmGauYWtcZ12py7pH2ZAWCFaeeLOgTFjZXfkw85Z4emlt/HQ+k DSJCtp51gcAhubqAv0bjYStkjGhtEjB3iNnSuoyiqzNF9mEXlyItP03ESQFJtFTC 7NICaLzeCnCJBbuFXe7VflUbTFxzdaSBbOpTO2TMlRmBCZLpQTMuY/F53mH9eShR UtkvICNHU0YUOQ9ULJVac+8xNYElnVd3c2wYBpjyohopgUvPYIxHkClJtu0j92p/ yZQ5UXnhCEIqbJiZrj6O =9vW5 -----END PGP SIGNATURE----- --GyRA7555PLgSTuth--