"bad interpreter: Input/output error"

[Jon LaBadie]

On Sun, Jan 14, 2024 at 03:53:29PM -0500, Jon LaBadie wrote:
>On Sun, Jan 14, 2024 at 08:31:11AM -0800, Jeff wrote:
>>
>> > Another confirmation of directory problems would be to
>> > temporarily add each of the above directories to your
>> > PATH variable:
>>
>>I already have the script directories in the path and have been able to
>>execute them simply using the script name without full qualification for
>>years.
>>
>> > Move test.py to "/" and check for expected behavior.
>>
>>It works.
>>
>> > Move it then to /mnt and recheck.
>>
>>It works.
>
>
>Did you continue moving the script down the rest of the directory
>path on the NAS?
>
>
>
>>
>>I just made a tiny little test script (test.sh) in my home directory
>>that consists entirely of:
>>
>>#!/bin/bash
>>python3 /mnt/WD8TBNAS03/Documents/ShellScripts/test.py
>>
>>And it works fine. So again, scripts *can* be executed from the NAS, but
>>the shebang line isn't honored, forcing me to explicitly state *what*
>>executes the script.
>
>Note, this is not "executing" the script from the NAS.  Python only
>needs to read, not "execute" the script file.
>
>That is one of the reasons I'd like to see if you can do ./test.py
>from your home directory with the executable located in each of the
>NAS directories.  I suspect that one NAS directory has permissions
>or ownership preventing execution.  It would be good to determine which.

Sorry, that should have been "test.py", not "./test.py"

-- 
Jon H. LaBadie                  ubu at labadie.us