Bug#684406: [condor-debian] Bug#684406: condor_rm did not remove actual running processes (PyMVPA searchlights)

2013-07-20 Thread Michael Hanke
Hi Andy, On Thu, Aug 09, 2012 at 03:38:55PM -0400, Andrew Connolly wrote: I suspect that when you removed the jobs, Condor killed the processes that it spawned, but didn't know about some child processes they had in turn spawned. Condor uses several techniques to track the child processes

Bug#684406: [condor-debian] Bug#684406: condor_rm did not remove actual running processes (PyMVPA searchlights)

2012-08-09 Thread Jaime Frey
On Aug 9, 2012, at 11:54 AM, Andrew C. Connolly wrote: Today I sent a large batch to condor (~50 jobs), then tried to kill the all with 'condor_rm andy'. This removed them from the condor_q list of running processes, but left them all actually running. I then had to kill them all manually

Bug#684406: [condor-debian] Bug#684406: condor_rm did not remove actual running processes (PyMVPA searchlights)

2012-08-09 Thread Andrew Connolly
I see that ipython has the ability to submit jobs into a batch system. Is this feature how you were submitting jobs into Condor? I did not use ipython to submit the jobs, I escaped the ipython shell with a leading ! before the call to condor, i.e.: @ipython_prompt[0]: !condor_submit

Bug#684406: [condor-debian] Bug#684406: condor_rm did not remove actual running processes (PyMVPA searchlights)

2012-08-09 Thread Jaime Frey
On Aug 9, 2012, at 2:38 PM, Andrew Connolly wrote: I see that ipython has the ability to submit jobs into a batch system. Is this feature how you were submitting jobs into Condor? I did not use ipython to submit the jobs, I escaped the ipython shell with a leading ! before the call to