David
NOTIFY ON and also - as this is a scheduler PHANTOM - change any long SLEEP
into smaller chunks of SLEEPS - e.g.
Instead of SLEEP 36000 try
FOR delay = 1 to 100; SLEEO 360; NEXT delay
There were two issues there (from my memory) - the first was that a BREAK on
a foreground process that had spawned a PHANTOM would wake the PHANTOM from
SLEEP. A side effect of the fix for this was that processes that launched
PHANTOMS had to get to a state to receive the signal generated when the
PHANTOM terminated (and a SLEEP was not a useful state).
Past fixes for PHANTOMs worth note in this context:
10.1.16
=======
8072 On LINUX and HP platforms, if a PHANTOM was executed from TCL,
the performance for subsequent TCL commands incurred a delay of
one second before processing while the PHANTOM process was active.
This problem has been fixed.
10.1.7
======
7247 On LINUX platforms, if a UniVerse process executed the TCL
NOTIFY ON command and that process has previously started a
nonsocket PHANTOM process that terminated, the parent process
did not detect that termination, and the PHANTOM process
became a zombie process until the parent process terminated.
In addition, on all UNIX platforms, when a UniVerse socket
server process excuted the TCL NOTIFY ON command and a
PHANTOM process started by the socket server was using the
socket connected to the socket server terminated, the server
did not detect the termination, and the PHANTOM process became
a zombie process until the socket server was terminated.
Both of these problems have been fixed.
Hope this helps
Regards
JayJay
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Norman, David
(SAAS)
Sent: 04 November 2007 22:52
To: [email protected]
Subject: [U2] Phantom creating Zombies
UV 10.0.16 (Information) HP-UX 11i
We have a permanently-running phantom, which needs to periodically start
another phantom, with both phantoms running independently. When the 2nd
phantom stops, that process becomes a zombie until the original phantom
stops (which is preferably just about never).
As these zombies mount up, we get to the situation where the id
associated with the phantom can't run processes or even login until the
zombies are cleared (by stopping the first phantom).
Our work-around is to stop and restart the first phantom weekly, but we
really don't want to have to do this.
It's no good just running the BP of the second phantom, because then the
first phantom pauses until the second phantom stops.
Is there a better way of one phantom launching another without the
zombie problem ??
Thanks,
========================
David Norman
Senior Software Engineer
SA Ambulance Service
Box 3, GPO
Adelaide, South Australia 5001
*+61 8 8274 0384
* fax +61 8 8271 4844
* [EMAIL PROTECTED]
-------
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/
