Date: Mon, 10 Aug 2009 19:04:07 +0200
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Can't execute scripts from a samba share with 1.7
Message-ID: <20090810170407.GX3204@calimero.vinschen.de>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <h5cqnj$c9f$1@ger.gmane.org> <20090806142010.GE3204@calimero.vinschen.de> <h5f54a$nkt$1@ger.gmane.org> <4A804DFD.6090609@dronecode.org.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4A804DFD.6090609@dronecode.org.uk>
User-Agent: Mutt/1.5.19 (2009-02-20)
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

On Aug 10 17:42, Jon TURNEY wrote:
> On 06/08/2009 18:50, Nahor wrote:
>> Corinna Vinschen wrote:
>>> On Aug 5 13:40, Nahor wrote:
>>>> If I mount with "noacl", I get a slightly different error but still
>>>> no cigar:
>>>> $ ./t.sh
>>>> -bash: ./t.sh: /bin/sh: bad interpreter: Permission denied
>>>> $
>>> This only happens if your account doesn't have execute permissions for
>>> the interpreter, in this case /bin/sh. Is it possible that /bin/sh.exe
>>> has weird permission settings for some reason?
>>
>> The permissions on the interpreter are OK.
>> $ ls -l /bin/sh
>> -rwxr-xr-x 1 nahor Administrators 472064 Jul 1 18:20 /bin/sh
>> $
>>
>> For that matter, scripts running off the local disk run fine.
>>
>> Looks like the same problem of inconsistent account ID, setting the
>> permissions to 755 or running as the domain user fix the "bad
>> interpreter" error.
>
> I also have this problem in it's second (noacl) form.  With this mount
>
> //necker/jon on /home/jon type smbfs (binary,exec,noacl,user)
>
> running the t.sh test script fails in a directory on this mount
>
> Jon@byron ~
> $ ls -al t.sh
> -rwxr-xr-x 1 Jon None 19 2009-08-06 15:46 t.sh
>
> Jon@byron ~
> $ ./t.sh
> -bash: ./t.sh: /bin/sh: bad interpreter: Permission denied
>
> but works fine in a different directory

This is really strange.  The bad interpreter message means that
bash could not start /bin/sh.  I can only reproduce this effect
if I chmod -x /bin/sh.  Did you create an strace and tried to
see what happens?


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

--
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