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:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=HF0oVe5I27m1YUV3VQj0us2MOz0khHkY48iF/BapUi9pFftjrJh+q
	y9StUUEApkAILTkOEVmuCcRm84q1ATKgaEy+aNJ8SzwihWfafZT4qP7Qygbcf2aS
	megfoIcK6h3uDLH4KYCW7OdeQlU17l27jrfPnUZqpWL9tQ3QVgwCL8=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Wed, 3 Sep 2014 15:04:20 +0200
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: (call-process ...) hangs in emacs
Message-ID: <20140903130420.GJ6056@calimero.vinschen.de>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <loom.20140828T172529-396@post.gmane.org> <loom.20140829T115632-276@post.gmane.org> <20140901115701.GD2644@calimero.vinschen.de> <87ppffs0kw.fsf@Rainer.invalid> <20140902083217.GM2644@calimero.vinschen.de> <87mwaiq6bt.fsf@Rainer.invalid> <20140902191914.GG6056@calimero.vinschen.de> <87sik9q069.fsf@Rainer.invalid> <20140902200907.GA18235@calimero.vinschen.de> <87oauxpy9v.fsf@Rainer.invalid>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;	protocol="application/pgp-signature"; boundary="pN9MePJoZbRKbUk1"
Content-Disposition: inline
In-Reply-To: <87oauxpy9v.fsf@Rainer.invalid>
User-Agent: Mutt/1.5.23 (2014-03-12)

--pN9MePJoZbRKbUk1
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sep  2 22:23, Achim Gratz wrote:
> Corinna Vinschen writes:
> >   $ setfacl -d g:system: filename
> >
> > Note the trailing colon.=20=20
>=20
> That's not what the man page specifies, however.  I'll keep it in mind.

I patched setfacl to not require trailing colons anymore.  This also
fixes a bug in terms of the allowed acl entries when deleting.

I now also fixed setfacl to add missing acl entries when modifying an
acl, same way as the Linux setfacl handles this.

And, this is important, given that setfacl now always creates complete
acls when modifying an acl, I could finally fix the aclcheck(2) function
in the Cygwin DLL to more thorougly test the incoming acl for all
required entries.

That means, when using the new Cygwin DLL, you also have to use the
accompanying setfacl(1).  With any older setfacl you'll suffer "setfacl:
Invalid argument" error messages.

I just created a new snapshot on https://cygwin.com/snapshots/
containing these patches.  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

--pN9MePJoZbRKbUk1
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBAgAGBQJUBxHUAAoJEPU2Bp2uRE+gsfsP/1r2GhaNQqzE7anQeRKM4VEA
t4TvET/wMQhKo88pLlaFyitAYXvsYU8Pf+EYkgtBNXf9B8xGLobvouT2pIDoNmNI
jiPdo9jX5FNpetlmYDHFIXhTpb4QOyVtnKl8yuL7j+7BxKcUxXC7M4h32XzoU1Mj
2+VGqjqpjM/cOfhUhT1edAmBUt7WJ/KUtsot9Mlsr0PdZqw7GV+zZmfuorMu6xZn
6lehEXxC29t2LkWBf5FZrNfvViouq2uuWh/IVr3vyvFvC7jHpa6OtPw1GPdFuV8D
Dth8mQYOE91/GZW6UMfcUgUErAGfg8d0jTcnUH7X9W/zbRcuphW7tvXGsocAhEAo
mh7Jg8KK4exMxSLQ8Hdd6LD/OInndNvaY+1HWjL4Wpo1yKODPJq3NpSZ05oxKWt4
FnBUZbdbau34UQ4PrA5q97CZjDYz85WUxE0cII5cAnW8rx1r+n930HnS93L4H5Sa
as9aGrVA3ck36JiTh+CXRx/ggyFah8ghY26rdgJFWXTz52f0yjl4MjTvLL1HSdxa
KHozMxoCtH0GhvjxFMATaZwTiN0nam+Nr0QZDk7bKERhRPoevHAbEuUXtvjDSbZZ
YVXXN5Nrt2vLhdgWXYyEtcMfVkOWpY551raR4iWPWZVus4XciBSzADHKkbr9N7BB
pElN/jCDjJn+r89AN9Hx
=QAkL
-----END PGP SIGNATURE-----

--pN9MePJoZbRKbUk1--