Carriage Return Character Causes Bad Interpreter

Add Comment | Related Links | TrackBack
Related Content

Carriage Return Character Causes Bad Interpreter

If you access UNIX shell scripts between platforms, such as Linux and Windows, then it's likely you encountered error message similar to the following in the past:


  -bash: ./script.sh: /bin/sh^M: bad interpreter: No such file or directory

This error message is caused by saving the "script.sh" file in an operating system--DOS, OS/2, and Windows--that uses carriage-return (CR) and line-feed (LF) as end-of-line (EOL) character sequence. UNIX platform uses the LF character for EOL. The "^M" character in the error message is the give-away, as it symbolizes for the CR character.

To fix the UNIX shell script, use our ConvertEOL (Freeware) command-line app to convert the script back to the UNIX format. ConvertEOL is written in Java, so it runs on any operating system with Java installed.

The following is a list of command sequences for UNIX shell to fix the script:


  java ConvertEOL script.sh t.sh
  mv t.sh script.sh
  chmod 700 script.sh

Chieh Cheng
Fri, 18 Nov 2011 21:38:07 +0000

Add Comment | Related Links | TrackBack
Related Content

Did your message disappear? Read the Forums FAQ.

Add Comment

Spam Control | * indicates required field

TrackBack

TrackBack only accepted from WebSite-X Suite web sites. Do not submit TrackBacks from other sites.

Send Ping | TrackBack URL | Spam Control

No TrackBacks yet. TrackBack can be used to link this thread to your weblog, or link your weblog to this thread. In addition, TrackBack can be used as a form of remote commenting. Rather than posting the comment directly on this thread, you can posts it on your own weblog. Then have your weblog sends a TrackBack ping to the TrackBack URL, so that your post would show up here.

Messages, files, and images copyright by respective owners.

Fun for Photographers