Stoopid script failure

[Paolo Galtieri]

On 02/06/2010 08:34 AM, Ed Greshko wrote:
> Ed Greshko wrote:
>    
>> Patrick O'Callaghan wrote:
>>
>>      
>>> Can anyone explain why this doesn't work? I've been writing shell
>>> scripts on and off for several decades and I can't see what's going on
>>> here. Is senility setting it?
>>>
>>> $ cat>  tst
>>> #!/bin/sh
>>> echo foo
>>> $ chmod +x tst
>>> $ ls -l tst
>>> -rwxrwxr-x 1 poc poc 19 2010-02-06 10:22 tst
>>> $ type tst
>>> tst is ./tst
>>> $ tst
>>> bash: ./tst: Permission denied
>>>
>>> (SElinux is off, if it matters).
>>>
>>>
>>>
>>>        
>> I'm fairly sure you need the ./tst incantation unless you have . in your
>> $PATH.  I recall somewhere, sometime a warning against that....but I've
>> ignored it for years and haven't had a problem.  I even forgot what the
>> warning was all about.
>>
>>
>>      
> I retract that last paragraph as rubbish...as I misread "permission
> denied"...
>
>    
check to see what shell /bin/sh actually refers to.  Usually /bin/sh is 
a link to /bin/bash but it doesn't have to be.  You can also try to run

   /bin/bash -x tst

and see what happens.

Paolo