X-Recipient: archive-cygwin AT delorie DOT com 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=cjyTm51D8zDFvks8 ymK9SYJ5tbr409oyH6HudU6lvfOg31msEDzdDr7ZcCa0UCtwjJ57SdexKUx0m+gm 2ljgbHmnrXwr0pez9rARae2LaeYbiFODlgcfjoWRD4nT4P6UystQ/TGlScStsjeP OJ3baUWEGZqdyVCenL1fOoqfNuY= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; 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; s=default; bh=hHlyv4v802McAAymHDftqh nfSew=; b=dbcRe1M+/poqs9imSvCoMSeLtsavj00DBCasZ5cczmKWkyD446USK0 FTjkwdevZ7lgj5E7TUlXInzOf/0hVCC/pUfle8yqMmKMywrHFjgZjJ36gf8+bPqK yS+3eDKIaD0zTY76ESDA7jMImEBJKSMpQL365s7at8SWrX7a6Br1I= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: Yes, score=6.1 required=5.0 tests=AWL,BAYES_60,FREEMAIL_FROM,KAM_THEBAT,SPF_SOFTFAIL autolearn=no version=3.3.2 X-HELO: smtp.ht-systems.ru Date: Thu, 25 Jun 2015 15:36:40 +0300 From: Andrey Repin Reply-To: cygwin AT cygwin DOT com Message-ID: <1122848749.20150625153640@yandex.ru> To: Rick Springob , cygwin AT cygwin DOT com Subject: Re: python binary retrieved via (cygwin) git clone does not execute - error 127 - SOLVED In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Greetings, Rick Springob! > I did an experiment. I copied the binary to another directory and executed > there. It worked! So, it was something about where the binary was rather > than what it was. > It turned out that the directory permissions were not correct: > # On the repo that works. > $ icacls windows > windows USWIN\V605040:(I)(F) > CREATOR OWNER:(I)(OI)(CI)(IO)(F) > USWIN\Domain Users:(I)(RX) > CREATOR GROUP:(I)(OI)(CI)(IO)(RX) > Everyone:(I)(OI)(CI)(RX) > # On the repo that does not work. > $ icacls windows > windows USWIN\V605040:(F) > USWIN\Domain Users:(RX) > Everyone:(RX) > CREATOR OWNER:(OI)(CI)(IO)(F) > CREATOR GROUP:(OI)(CI)(IO)(RX) > Everyone:(OI)(CI)(IO)(RX) > The directory did not inherit permissions from its parent. Using explorer I > went to the advanced security settings and checked the "Replace all child > object permissions with the inheritable permissions from this object." > Voila! The failing binary started working. > Not sure that this is a cygwin/git bug. I would think this behavior would be > more widely reported if it was a bug. It is a Cygwin, but it is not a bug, rather - intended behavior. You can get around it by setting "noacl" flag on mount points you want to be managed by Windows, or explicitly chmod +x necessary binaries. (Though, they SHOULD be chmod'd in the git. Else it is just not suitable for the job of VCS.) > It is more likely that the problem was caused by either a security policy or > the "IT approved" version of cygwin had been modified. Company issued > laptops are heavily managed by IT department where I work. (And, dog slow > because of all the installed nannies.) .........no comments. -- With best regards, Andrey Repin Thursday, June 25, 2015 15:33:56 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