Shell Programming and Scripting

execute the below command

Code:

perl -pi -e 's/\r\n/\n/g' scriptname.sh

then try to run your command.

@ balajesuri
This is the cat -A mytest.sh:

Code:

#!/bin/bash^M$
var1=`ps -ef | grep -v grep | grep cleanlog| awk '{print $2}'`^M$
echo $var1^M$
if [ -n "$var1" ]^M$
then^M$
echo "Process running"^M$
else^M$
/usr/bin/php -q cleanlog.php^M$
fi

I tried using your command

sed 's/<ctrl+v+m>$/\n/' mytest.sh

It still doesnt work with /bin/bash mytest.sh

@Scrutinizer
Tried with this command:

Code:

tr -d '\r' < mytest.sh > mynewtest.sh

And then execute with

Code:

/bin/bash mynewtest.sh

Wow great !! It works !

@ Sangarasan
Thanks.

Thank you guys,, you are all great ! I'm learning lot from you all.

@franx47: I missed this: Not all seds support \n in its replacement.

In some tr also \r is problem, but using octal value has worked always.

Code:

cat file | tr -d '\015' > newfile

# or

tr -d '\015' < file > newfile

What tr has a problem with \r? It is POSIX compliant and even default tr on Solaris supports it

even posix - . Same as RFC, there is lot of code makers who has not read those pages, starting from Seattle.

I have used so many *nix system which we have used in the our customers environment. I don't remember which env it was and I'm not interested. I'm interested that our scripts works without any modification in the every our customers *nix systems. There is lot of mainframe *nix envs which has not updated. As we know standards has written after many tools has done. Ex. many *nix still use ksh88, not ksh93, even 1993 was some years ago.

With tr I have found problem using \-escape sequences in history => We use always octal format.

Here is what the POSIX spec says about this:
tr: Rationale
I am not sure why it says it is not portable..