Re: sh <scriptname> malfunction after upgrade

["J. Bakshi" <bakshi12@gmail.com>]

On Wed, 9 Nov 2011 12:34:57 +0100
Jochen Spieker <ml@well-adjusted.de> wrote:

> J. Bakshi:
> > 
> > I have upgraded a very old lenny server to squeeze.
> > The shell scripts are now malfunctioning; specially the
> > loop statement. Moreover "sh -x <script>" are malfunctioning
> > but :bash -x <script>" are running fine. what actually I am missing
> > here ? I have tried both with #!/bin/bash and #!/bin/sh but the same
> > problem with "sh -x <script>"
> 
> /bin/sh points to dash nowadays. You need to either run "bash -x
> <script>" or use "set -x" in the script.
> 

Thanks , so is it a backward compatibility ?
Shall I place "set -x" just after #!/bin/bash ?

Thanks