Mark Klein wrote:
>
> Jeff, learning his way, asks:
>
> >In the CI I could have turned on command tracing (HPCMDTRACE
> >variable).  I could have done an :ERRDUMP command.  Except if
> >OPTION NOHELP was specified, the CI would have echoed the bad
> >command with a caret under the bad parm (but not which file it was
> i>n).  Are there similar tricks one can do in the shell?
>
> Yes. The quickest way is to invoke the shell script under an
> invocation of the shell with -v on it:
>
>         /bin/sh -v ./sendmail-8.11.3/devtools/bin/configure.sh

In addition to -v, there is also -x.  You can also edit the first line of a
shell script to specify these flags for each run of the script, i.e.:

#!/bin/sh -x

Be aware that using -v or -x in one script can confuse other scripts that might
be processing the output of the first script.
--
[log in to unmask]
Remainder of .sig suppressed to conserve scarce California electrons...

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *