Normally, scripts don't go on until a subprocedure is done. But there are ways to make it do so, and you're most likely using one of them. However, you're not showing any code, so it's hard to tell what you're doing incorrectly.

A couple things off the top of my head are:

• You could be using forks or threads in your program.
• You could be executing shell commands and explicitly putting them in the background (such as when using the '&' operator in bash).
• There could be a timeout implemented (such as with signal and a timer) that's terminating the program earlier than expected.

There are other ways, too, of course. If you'd show a bit of code, perhaps someone could help you identify the problem.

...roboticus

When your only tool is a hammer, all problems look like your thumb.