[NTLUG:Discuss] Why does nfs wreck shell scripts?

[Fred James]

Call me silly, but bear with me just to be sure, OK.
"test" is a built-in shell command, and therefore it is generally 
accepted that it, like other built-in shell commands, is not a good name 
for a shell script, and a few other things.
So, just to be sure we aren't looking at something like that, please 
rename you script and try again.
That would be "step one" in my mind.


Lance Simmons wrote:

>I'm playing around with nfs at home. When I've got a bash script on an
>nfs-mounted filesystem, I can't execute it directly. Consider this
>script, named "test":
>
> #!/bin/sh
> echo "test"
> exit 0
>
>When I try to execute test directly (./test), I get this error:
>
> bash: ./test: /bin/sh: bad interpreter: Permission denied
>
>When I try to execute test with the command "sh ./test", it works.
>
>Can someone knowledgeable about nfs explain what this is about? I
>imagine it's something pretty simple. I'm probably misunderstanding the
>metaphysics of nfs, but I'm not sure where to look.
>

-- 
small is beautiful