When the shell script is executed, the solution of & quot; bad interpreter: Text file busy & quot; is interpreterbusy.

Solution for "bad interpreter: Text file busy" during shell script execution, interpreterbusy

When executing a shell script, an error message "-bash:./killSession. sh:/bin/bash: bad interpreter: Text file busy" is displayed, as shown below:

[Oracle @ DB-Server bin] $./killSession. sh
-Bash:./killSession. sh:/bin/bash: bad interpreter: Text file busy

In this case, you only need #! /Bin/bash, add a space #! /Bin/bash to solve the problem.

In another case, you can use lsof | grep killSession. sh to check whether other processes are accessing the file.

You can run the kill command to kill other processes. Solve the problem above.

When executing the shell script, the prompt is bash:/shellsh: bin/bash: bad interpreter: No such file or directory.

Are you sure that the first line of your script is #! /Bin/bash: From the error message, you write as if it is bin/bash, with fewer/

Shell script-bash:/sh_ext_ztdztd:/bin/csh: bad interpreter: Permission denied how can this problem be solved?

-Bash indicates that your local shell is bash.
But the shell interpreter declared at the beginning of the script is/bin/csh,
Therefore, the following error occurs: "interpreter not found" and bad interpreter.

In addition, the error Permission denied may be because the script execution Permission is not granted.
Chmod + x./sh_ext_ztd.ztd
Execute scripts