[SOLVED] shebang error

bkelly · 08-31-2018, 10:51 AM

I am running a network boot version of Centos. All the people that know anything about it are out for an extended period.

My bash scripts all start with this first line:

Code:

#!/bin/bash

Every time a script is run the monitor looks like this:

Quote:

bash-4.25 ./test_for.sh
./test_for.sh: line1: #!/bin/bash: No such file or directory

So do this:

Quote:

bash-4.25 ls -al /bin/ba*
-rwxr-xr-x 1 root root 32352 Apr 10 21:35 /bin/base64
-rwxr-xr-x 1 root root 29032 Apr 10 21:35 /bin/basename
-rwxr-xr-x 1 root root 964544 Apr 10 17:35 /bin/bash
lrwxrwxrwx 1 root root 10 Jun 11 16:27 /bin/bashbug -> bashbug-64
-rwxr-xr-x 1 root root 6964 Apr 10 17:52 /bin/bashbug-64
-rwxr-xr-x 1 root root 137 Apr 10 17:13 /bin/batch

As I read it, everything is in place.
This error might be related to this thread:

https://www.linuxquestions.org/quest...04#post5898404

But to the best of my ability bash is working as it should.
Are there any suggestions as to what this might be trying to tell me?

rtmistler · 08-31-2018, 11:04 AM

As I read it, you have two bash executable files in your /bin directory, of different sizes:

Code:

bash-4.25 ls -al /bin/ba*
-rwxr-xr-x 1 root root 32352 Apr 10 21:35 /bin/base64
-rwxr-xr-x 1 root root 29032 Apr 10 21:35 /bin/basename
-rwxr-xr-x 1 root root 964544 Apr 10 17:35 /bin/bash
lrwxrwxrwx 1 root root 10 Jun 11 16:27 /bin/bashbug -> bashbug-64
-rwxr-xr-x 1 root root 6964 Apr 10 17:52 /bin/bashbug-64
-rwxr-xr-x 1 root root 137 Apr 10 17:13 /bin/bash

I would determine what the problem is there first. These are both files, no links. Both have 755 permissions.

bkelly · 08-31-2018, 11:10 AM

Aw crum. that last entry should have been batch rather than bash. When I attempted to proof read I saw "bach" and rather than adding a "t" is changed the c to s.
The OP has been corrected and my apologies

smallpond · 08-31-2018, 11:11 AM

Did you create the script on Linux or Windows?

NevemTeve · 08-31-2018, 11:16 AM

Yes this must be some invalid character problem like BOM or CR.
https://www.linuxquestions.org/quest...0/#post5725686

rtmistler · 08-31-2018, 11:41 AM

What smallpond and NevemTeve said.

If you have dos2unix on your system, use that to convert the file.

Or if you have hexdump you can dump the script and see for yourself if it has 0d 0a or just 0a [(CR LF) = DOS or (LF) = Unix/Linux]

bkelly · 08-31-2018, 12:49 PM

You are on to something.
When I hex dump that file the first three characters are, in hex, EF BB BF

Created a new file from scratch and the first three are: 23 21 2F These are the #!/

I cannot imagine where those three byte came from. The Linux box and the Windows box are two completely separate computers. I cannot move any data from either one to the other. When the first few lines of the errant file are deleted and save, those three lines remain. When the cursor is put then home puts the cursor on the # and end puts it on the h of bash.

So for all my scripts I must start a new file and copy the text in from the old, skipping the first line or two and entering those by hand.

So this is resolved.
Thank you.

NevemTeve · 08-31-2018, 02:13 PM

https://en.m.wikipedia.org/wiki/Byte_order_mark