Mansur, Warren writes:
> I'll try putting echoes on each
> line to see where it might break.
You might try putting "set -x" somewhere near the top. This causes
the shell to echo what it is doing. I've found this to be useful when
debugging large shell scripts.
(turn this off with "set +x")
> Now I can get
> back to coding . . . ugh.
Hey, I *like* coding... (-:
--kevin
--
Kevin D. Clark | |
[EMAIL PROTECTED] | [EMAIL PROTECTED] | Give me a decent UNIX
Enterasys Networks | PGP Key Available | and I can move the world
Durham, N.H. (USA) | |
**********************************************************
To unsubscribe from this list, send mail to
[EMAIL PROTECTED] with the following text in the
*body* (*not* the subject line) of the letter:
unsubscribe gnhlug
**********************************************************
