On Sat, Aug 30, 2008 at 11:07 AM, Eric Wertman <[EMAIL PROTECTED]> 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 w
> 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 t
Glenn Hutchings wrote:
Have you checked memory usage while your program is running? Your
lines = f.readlines()[2:]
statement will need almost twice the memory of your largest file.
footnote: list objects contain references to string objects, not the
strings themselves. the above tempo
dieter wrote:
Any Ideas? Is there a buffer limitation? Do you think it could be the
filesystem?
what does "ulimit -a" say?
--
http://mail.python.org/mailman/listinfo/python-list
On 28 Aug, 07:30, dieter <[EMAIL PROTECTED]> 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 o
dieter <[EMAIL PROTECTED]> writes:
> 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 be
dieter wrote:
> Hi,
>
> Overview
> ===
>
> 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 t
Hi,
Overview
===
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
