Posted by Jim Guerber on May 11, 2006 at 11:56:47:
In Reply to: Multiple Instances of Comet Not Multiple Sessions posted by Jon Sacks on May 10, 2006 at 11:13:23:
This is a good question and deserves quite a bit of consideration.
We provide two programs for terminating Comet. Qipl checks to see if any processes are currently running on the system and if one or more were currently running, it would display that fact and wait for user response. Qipl0 unconditionally terminates the session if not session zero and unconditionally terminates comet if session zero.
If Comet as a service were running on this machine, all sessions could end gracefully by running qipl0. session zero would terminate, but Comet would continue to run. The next time someone clicked on a shortcut to "start Comet", session zero would re-appear.
If you really want Comet to terminate when the last job is finished, you (or we) should make a modification to the qipl program that knows if it is the primary session and if so, waits until all other sessions are clear and then runs qipl0.