> 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".
This is the behavior you'll see when your os has run out of some memory resource. The kernel sends a 9 signal. I'm pretty sure that if you exceed a soft limit your program will abort with out of memory error. Eric -- http://mail.python.org/mailman/listinfo/python-list
