On Thu, Oct 22, 2015 at 02:39:43AM +0000, Kai Wang X wrote: > The process named "com" launched by script command "com.sh start". Pls refer > to the attached files. It looks easy, doesn't it?
It looks like a horrible mish-mash of legacy Bourne shell syntax, edited later by another person using certain post-Bourne shell constructs (note the inconsistent use of test and [ commands), with quoting failures thrown in for good measure (lots of [ -e ${foo} ] commands). I cringed at the `expr` all over the place, and stopped reading halfway through. The shebang is #!/bin/sh and it's using half-Bourne half-POSIX code, so if you suspect a bug in bash, why not just let it run under some other shell? /bin/sh does not link to bash on most operating systems. Not even on all of the Linux-based operating systems.