Shulou(Shulou.com)06/03 Report--

This article focuses on "how to solve the problem of" not having that file or directory "when executing a shell script. Interested friends may wish to have a look. The method introduced in this paper is simple, fast and practical. Let's let the editor take you to learn "how to solve the problem of" not having that file or directory "when executing a shell script."

The reason for bad interpreter:No such file or directory is the file format. This file is written under Windows. The way of line wrapping is different from that of Unix, but you can't see it without Set under vim.

Problem analysis:

1. Transfer the SHELL file written under windows to linux for execution, indicating an error.

2. Error message: bad interpreter: there is no file or directory.

The cause of the problem:

Because the operating system is windows, the script is edited under windows, so there may be invisible characters. The script file is in DOS format

That is, the end of each line is marked by\ r\ n, and its ASCII codes are 0x0D and 0x0A respectively.

Solution:

There are many ways to see whether the file is in DOS format, UNIX format or MAC format

(1) vim filename

Then use the command: set ff

You can see the words dos or unix, if it is indeed in dos format, then use set ff=unix to force it to unix format, and then save the disk to exit and run it.

To convert text file formats on different platforms, you can use

1. Unix2dos or dos2unix these two Mini Program to do. It's simple。 In djgpp, the names of these two programs are dtou and utod, with u for unix and d for dos

two。 You can also use tools like sed to do this:

The code is as follows:

Sed's / ^ M / / 'filename > tmp_filename

Mv-f tmp_filename filename

Special note: ^ M is not the ^ and letter M generated by pressing shift + 6, it is a character, its ASCII is 0x0D, the way to generate it is to press CTRL+V first, and then enter (or CTRL+M)

In addition, when the SHELL program reports command not found, always check your PATH to see if there are every command that the program uses (the one that doesn't specify an absolute path). A program as small as yours can be checked one by one.

Attachment: write one less / cause no file or directory problem

Today, when I was flipping through a simple shell script I wrote before, I found a problem:

When the. / runtime always prompts: (bash:. / hello.sh: bin/bash: bad interpreter: there is no such file or directory), but it is correct when running with sh.

The original script:

(see if you can see the mistake at a glance.)

The code is as follows:

#! bin/bash

Echo "Hello Linux!"

Later, several checks found that something was missing from what I had written.

The first line should be changed to #! / bin/bash, with one less /

Alas, it's a very simple question. I didn't find such a mistake before! Shell scripts are really easy to use, but the only difficulty is that the format is too demanding!

At this point, I believe you have a deeper understanding of "how to solve the problem of" there is no file or directory "in the execution of the shell script. You might as well do it in practice. Here is the website, more related content can enter the relevant channels to inquire, follow us, continue to learn!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.