I believe this is a Python Gump message. I've fought (and fought, and re-written, and fought) Python here. Trying to get a portable/workable 'kill off spawn' has failed. I've read documentation, I've read cookbooks, nothing seems to give what we need -- i.e. kill off grandchild processes.
All inputs welcomed. regards Adam ----- Original Message ----- From: "Stefan Bodewig" <[EMAIL PROTECTED]> To: <[email protected]> Cc: "Steve Cohen" <[EMAIL PROTECTED]> Sent: Wednesday, January 12, 2005 6:51 AM Subject: Kaffe fails to kill subprocesses (was Re: Killed a bunch of undead Kaffe processes) > Hi, > > during the current Kaffe run, commons-net's unit tests timed out and > the builds ends with > > > Kill all child processed (anything launched by PID21010) > > unfortunately it doesn't. During the tests, commons-net starts some > server processes that bind to TCP ports and those ports are still in > state LISTEN (and lsof list kaffe-bin as owner). > > So far this has caused the commons-net builds on Sun VMs to fail as > well, since they assumed the ports would be free. Steve Cohen hopes > he's patched the tests to work around the problem. Let's keep our > fingers crossed. > > Anyway, when Kaffe tries to kill the spawned subprocesses, it > sometimes fails. Maybe this happens because the processes are > grandchildren of the PID listed in the message. > > Stefan > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
