What I was trying to say, and what BUU tried to say as well, is that while you may indeed have good reasons to do "something like" the above, all in all it seems awkward.

Just like java -jar gogo.jar has to terminate before the system call returns, so has -say- bash. And to terminate, if it is interactive, it has to be told so.

Now the point is: if you launch those shells, it seems that you want to allow the users of your program to perform arbitrary operations, don't you? If so, I don't see any obvious alternative to the current behaviour. Or else you should change the whole logic around...

Last, I may be utterly wrong, but the above also suggests that your program may look much like a shell script. If this is the case, you may consider writing an actual shell script instead. If not, then plainly ignore this piece of advice!