X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.4 required=5.0 tests=AWL,BAYES_00,TW_HR,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-class: urn:content-classes:message Subject: FW: cygwin 1.7.13-1: can't execute shell scripts on samba share Date: Mon, 23 Apr 2012 14:58:27 +0200 Message-ID: <6BFA9AF2C7556E42AFF3F187ECAB07B802F9CFEA@bespdc01.mediaxim.local> From: "Michel Bardiaux" To: X-IsSubscribed: yes 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 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by delorie.com id q3NCxDHX017596 Sorry, forgot to change the recipient. -----Original Message----- > [snip] > >> lgiambro AT lorien ~ >> $ cat len.sh >> #!/bin/sh >> echo it works > > And man sh states " --norc Do  not  read  and  execute the personal > initialization file ~/.bashrc if the >              shell is interactive.  This option is on by default if > the shell  is  invoked >              as sh." > Which eliminates bashrc as a possible culprit. > bash as sh will use ~/.profile in interactive and -login mode. Yes, I forgot about .profile. The OP should check his .profile does nothing that could cause it to fail when the current directory is a samba share. > My guess is the remote disk handler is causing Cygwin to not see the file as executable. Then why would getfacl, and ls, say it *is* executable? (In the OP case; in my case you are absolutely right).