Well, since there isn't a reply yet, I do have a quick hack that will get around this issue. I'm afraid it's the best I know how to do, though:
Code:
/usr/bin/screen -d -m /path/to/myprogram
If you don't know about screen, it is a very handy program which becomes the output console for the program. You can pull it up later (while the program is running) for the output... or in this case, not. the two switches "-d -m" mean to start the program and immediately disassociate itself from the current console. When "myprogram" finishes, screen will close without any messages to the user. It will use a tiny bit more memory since you will be launching two programs, but on most systems made in the last few years it isn't enough to worry about.