Process "Killed"

Paul Boddie paul at
Fri Aug 29 21:25:07 CEST 2008

On 28 Aug, 07:30, dieter < at> wrote:
> I'm doing some simple file manipulation work and the process gets
> "Killed" everytime I run it. No traceback, no segfault... just the
> word "Killed" in the bash shell and the process ends. The first few
> batch runs would only succeed with one or two files being processed
> (out of 60) before the process was "Killed". Now it makes no
> successful progress at all. Just a little processing then "Killed".

It might be interesting to check the various limits in your shell. Try
this command:

  ulimit -a

Documentation can found in the bash manual page. The limits include
memory size, CPU time, open file descriptors, and a few other things.


More information about the Python-list mailing list