Actually, I've found another solution. If I put an entry in the Universe VOC called UV.LOGIN with the following value:
001 PA 002 NOTIFY ON This takes care of the problem. When the spawned phantoms complete, they want to go back to the process that started them and say, "Hey, I'm done!". The problem with this is by default, this doesn't occur until the process that spawned the phantom gets a new TCL prompt. Since they were spawned by another phantom process, there will never be a new TCL prompt and this will use up all the available unix processes eventually because all of the spawned phantoms are waiting to die. NOTIFY ON tells these phantoms to just display your, "Hey I'm done!" message without waiting for a new TCL prompt. The phantom processes can then die, freeing up a unix process. This works, and it was a lot easier to do. Thanks, Nick Cipollina -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of George Gallen Sent: Monday, August 02, 2004 10:06 AM To: [EMAIL PROTECTED] Subject: RE: [U2] [UV] Phantom Problem if the phantom is still running, I've found that any phantoms spawned by that phantom will not fully die until the parent phantom process is no longer. if the parent phantom is a loop, which in it's loop spawns off the other phantoms, instead of repeating the loop, have it chain back to itself CHAIN "PHANTOM LOOPING-PHANTOM" That will end the original process, and any child processed spawned will return their process id's back to the system, otherwise you will eventually run into the unix problem of "new available processes", and the system will start to drrrraaaaaagggggggggg. George >-----Original Message----- >From: Nick Cipollina [mailto:[EMAIL PROTECTED] >Sent: Saturday, July 31, 2004 3:27 PM >To: [EMAIL PROTECTED] >Subject: [U2] [UV] Phantom Problem > > >We are having a problem with our phantom processes. We have a job that >runs as a phantom that spawns many phantom processes. When these many >phantom processes die, they are leaving behind a <defunct> process. >This is cause when the phantom process attempts to notify the process >that started it that they are complete. Since they were started by a >phantom, there is no process to notify. I've run into this before, but >I don't' remember how we resolved it. I got my solution from this user >list, and I'm hoping that someone can refresh my memory. Thanks in >advance. > > > >Nick Cipollina > > > >Pick Programmer > >ACS - Heritage Information Systems, Inc. > >2810 North Parham Road, Suite 210 > >Richmond, VA 23294 > >(804)644-8707 x 314 > >[demime 1.01d removed an attachment of type image/jpeg which >had a name of image001.jpg] > >[demime 1.01d removed an attachment of type image/gif which >had a name of image002.gif] >------- >u2-users mailing list >[EMAIL PROTECTED] >To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [EMAIL PROTECTED] To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [EMAIL PROTECTED] To unsubscribe please visit http://listserver.u2ug.org/
