George, Are you saying that a phantom process launched from another phantom process "hangs around" in a defunct state after completing until the parent phantom process ends? Ouch!
Thanks for you feedback. ...ds ________________________________ From: [EMAIL PROTECTED] on behalf of George Gallen Sent: Fri 5/19/2006 11:16 AM To: [email protected] Subject: RE: [U2] Phantom job started from another phantom job After sleeping, instead of the process repeats itself, what you need to do is CHAIN"" to itself, this will end that phantom, which will release all it's child processes from their zombie status. If you continue to build up zombies, without releaseing them, you will eventually get the dreaded "no more processes available" message, at which point, UV comes to grinding crash halt, until you kill that one repeating phantom, then magically, all the processes become available again, and UV picks itself up and continues on with life. The only problem with this method, is you will build up a crap load of very small files in the &PHANTOMS& file. We have a process which every few days deletes old fileid (using the ls to give us the date the file was created, and made our &PHANTOMS& file a type 19) Oh, and YEA, looks like the reply is back to the way it was. George > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Scott, Dave > Sent: Friday, May 19, 2006 10:56 AM > To: [email protected] > Subject: [U2] Phantom job started from another phantom job > > > A colleague of mine ask me to post this on his behalf. > > I have a Phantom job that runs continuously. The job performs > a select, > executes some processing on the records returned from the > select, and then > goes to sleep for a few minutes. After sleeping, the process > repeats itself. I > recently added an additional step after the processing. This > step starts > another Phantom process which launches a program that does a > select and > processes the results of the select and then stops (using > CHAIN "OFF"). > > The problem is that our system admins have noticed that the > "child" Phantom > processes launched by the parent Phantom process go into a > state of "defunct" > from a Unix process perspective. > > $ ps -ef | grep defunct > fhooven 23180 986 18 16:33:12 ? 0:00 <defunct> > dscott 23302 23199 1 16:33:32 pts/tW 0:00 grep defunct > > The child Phantom process runs successfully and the "defunct" process > eventually goes away. > > Any idea what causes this? > > System is Universe 10.0 running on HPUX B.11.11 A > > Thanks for you help. > > ...Frank Hooven > ------- > 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/ [demime 1.01d removed an attachment of type application/ms-tnef which had a name of winmail.dat] ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
