bad interpreter: No such file or directory

sadashiv.linux · 09-19-2007, 05:15 AM

bad interpreter: No such file or directory

I also got above error; so I was looking going through this topic.
Just to add -- this error also comes when no perl is installed on your system.
While trying command "perl -i -pe's/\r$//;' <file name here>" I come to know about this

Thanks!!!

Sadashiv

cnschulz · 02-25-2008, 11:09 PM

Quote:

Originally Posted by mahantesh_hongal

Dear wbrummet. Thanks a billion.

Your simple perl command (perl -i -pe's/\r$//;' <file name here>) clears up my issue

Thanks,
Mahantesh Hongal

thanks, your cr/lf suggestion is still helping people!

c.

deepdash · 04-22-2008, 02:17 AM

Thanks XunXu and wbrummet!

Both these worked -

dos2unix <filename>

perl -i -pe's/\r$//;' <filename>

tieuphongvan · 04-24-2008, 05:16 PM

Either using the perl command:

Code:

perl -i -pe's/\r$//;' <file name here>

or trying to ftp the script from a Windows-based machine to a Unix-based machine while NOT under binary mode will do the job

Thanks to both wbrummet and timmeke!

peterlombardo · 06-16-2008, 05:06 PM

Quote:

Originally Posted by tieuphongvan

Either using the perl command:

Code:

perl -i -pe's/\r$//;' <file name here>

or trying to ftp the script from a Windows-based machine to a Unix-based machine while NOT under binary mode will do the job

Thanks to both wbrummet and timmeke!

I had this issue which drove me nuts. I was familiar with dos2unix and the variations of line feeds...but still nothing fixed it and it still didn't execute.

As it turns out, the script I was trying to execute was on a external USB drive mounted with the 'noexec' option. doh! Move the script to local hard drive (mounted without 'noexec' obviously) and everything works...

Regards,
Peter

gaurav.s.agrawal · 11-14-2008, 03:16 PM

I was facing the same problem and converting from dos to the uniz format did the trick

Samurai Unix · 01-15-2009, 09:11 AM

Quote:

Originally Posted by wbrummet

I have run into this problem many times when editing scripts on a windows based system then FTP'ing them onto my servers. I simple Perl command always seems to clear up the problem. Try the following command on your text file then try and run it.

perl -i -pe's/\r$//;' <file name here>

Thanks. This script worked for me as well. What does it do?

irwinr · 03-19-2009, 09:47 AM

Quote:

Originally Posted by timmeke

A lot of the commands (using tr, perl, ...) posted here all do pretty much the same as the "dos2unix" utility mentioned. Please use this utility, as it was specifically created for this CR\LF issue.

Yes, dos2unix may be preferred, but it's not always installed. I ran into this issue today with a server that did not have a dos2unix command but did have perl installed, so the perl one liner here saved me a bit of time.

We should encourage alternative solutions, not discourage them.

-Jeremy

ErV · 03-19-2009, 11:10 AM

Quote:

Originally Posted by Samurai Unix

Thanks. This script worked for me as well. What does it do?

It changes line endings from windows to unix format.

Quote:

Originally Posted by irwinr

We should encourage alternative solutions, not discourage them.

-Jeremy

The thread is dead. First message is from 2004.

JZL240I-U · 03-19-2009, 11:22 AM

Quote:

Originally Posted by ErV

...The thread is dead...

It's not, since you just posted

.

tieuphongvan · 03-20-2009, 12:16 PM

Quote:

Originally Posted by JZL240I-U

It's not, since you just posted

.

It took 1 yr for a good solution, and there are still people looking for the same solution after 5 yrs....Long live thread, woot

manishsingh4u · 04-01-2009, 05:01 PM

This worked great.

Code:

perl -i -pe's/\r$//;' <file name here>

Thanks.

Manish

chrism01 · 04-03-2009, 07:42 PM

I'd be surprised if dos2unix is not part of the std install these days..

mwdmarco · 03-30-2010, 06:51 AM

I had the same problem as everybody who has been asking here.
I tried some of the suggested ideas but still no success
The way I have fixed it is by removing the top line

#!/bin/bash

once I removed that, is working very well

Hope this helps

Marco

theRiley · 11-11-2010, 11:50 AM

Quote:

Originally Posted by nx5000

Put this in .vimrc

" Add keymappings
map <F4> :set fileformat=unix<CR>
map <F5> :set fileformat=dos<CR>

Then use F4/F5 for changing fileformat

thanks, this gets to the heart of the problem, and provides a solution.

coming from the unix side, hadnt realized that linux vi defaulted (at least in my RHEL distro) to dos crlf behavior.

which is bad imo, since it breaks intrinsic functionality.