Since you’re on windows you could just have you initial process create and become part of a job object http://msdn.microsoft.com/en-us/library/ms684161%28v=vs.85%29.aspx http://msdn.microsoft.com/en-us/library/ms684147%28v=vs.85%29.aspx then set JOB_OBJECT_LIMIT_KILL_ON_JOB_CLOSE Here’s a little guide http://stackoverflow.com/questions/53208/how-do-i-automatically-destroy-child-processes-in-windows This requires >win2k (but that’s losing condor support anyway so shouldn’t be a problem J) From: condor-users-bounces@xxxxxxxxxxx [mailto:condor-users-bounces@xxxxxxxxxxx] On Behalf Of Michael O'Donnell I believe the Condor team has worked on eliminating the issues related to Condor not being able to track forked processes on execute machines, but I seem to be having a similar issue when spawning processes with Python.
-------------- Gloucester Research Limited believes the information provided herein is reliable. While every care has been taken to ensure accuracy, the information is furnished to the recipients with no warranty as to the completeness and accuracy of its contents and on condition that any errors or omissions shall not be made the basis for any claim, demand or cause for action. The information in this email is intended only for the named recipient. If you are not the intended recipient please notify us immediately and do not copy, distribute or take action based on this e-mail. All messages sent to and from this email address will be logged by Gloucester Research Ltd and are subject to archival storage, monitoring, review and disclosure. Gloucester Research Limited, 5th Floor, Whittington House, 19-30 Alfred Place, London WC1E 7EA. Gloucester Research Limited is a company registered in England and Wales with company number 04267560. -------------- |