Rick Mann wrote:
No worries. In answer to your earlier question, I don't control the other code. Well, I do (it's open source), but I don't want to change it. It's a complex Java servlet container.
A "tender" process might work. Instead of spawning the target process directly, you spawn a tender whose sole job is to spawn the target process and wait for it to die, then communicate that event back to your initiating process in whatever way you want. The tender is written and controlled entirely by you, so you can have it perform whatever actions you want: IPC, distributed notification, etc.
The /usr/bin/time command is somewhat like this, in that it runs another command with the purpose of reporting the child's execution time. The bash shell also has a builtin 'time' command.
-- GG _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
