How to solve / bin/ bash ^ M: bad interpreter error report in Linux

The editor of this article introduces in detail "how to solve / bin/ bash ^ M: bad interpreter errors in Linux". The content is detailed, the steps are clear, and the details are handled properly. I hope this article "how to solve / bin/ bash ^ M: bad interpreter errors in Linux" can help you solve your doubts. Let's follow the editor's ideas to learn new knowledge.

Reason:

The error prompted when executing a shell script is mainly due to the fact that the shell script file is in dos format, that is, the end of each line is identified by\ r\ n, while the end of the line in unix format is identified by\ n

Solution:

(1) use the linux command dos2unix filename to directly convert the file to unix format

(2) use the sed command sed-I "s /\ r filename /" filename or sed-I "s / ^ M / /" to directly replace the Terminator to unix format.

(3) vi filename opens the file, executes: set ff=unix sets the file to unix, then executes: wq, saves it to unix format.

There are several ways to see if the script file is in dos format or unix format.

(1) cat-A filename can judge from the display result that the end of the file line in dos format is ^ M, and the end of the line in dos format is

(2) od-t x1 filename if you see the character 0d 0a in the output, then the file is in dos format, and if only 0a is in unix format

(3) vi filename opens the file and executes: set ff, if the file is in dos format, it is displayed as fileformat=dos, if it is unxi, it is displayed as fileformat=unix.

After reading this, the article "how to solve / bin/ bash ^ M: bad interpreter errors in Linux" has been introduced. If you want to master the knowledge points of this article, you still need to practice and use it before you can understand it. If you want to know more about related articles, welcome to follow the industry information channel.