Bob Smith wrote:
Peter Hansen wrote:
Bob Smith wrote:
Attached is the code. Run it yourself and see. You too Peter. Be
gentle with me, this was my first attempt with threads.
Thanks, Bob, and I will, but not before you answer some of my
questions.
I had good reasons to ask them, one of which is t
Bob Smith <[EMAIL PROTECTED]> wrote:
> Attached is the code. Run it yourself and see.
This seems to run nmap over series of consecutive IP addresses. nmap
can do that all by itself. From its man page::
Nmap also has a more powerful notation which lets you specify an IP
addres
Peter Hansen wrote:
Roel Schroeven wrote:
Peter Hansen wrote:
How have
you proven that it is not *that* program which is at fault?)
It would surprise me: even if it consumes much CPU-time, memory and
other resources, each instances returns all resources when it exits.
I agree with that statement
Roel Schroeven wrote:
Peter Hansen wrote:
How have
you proven that it is not *that* program which is at fault?)
It would surprise me: even if it consumes much CPU-time, memory and
other resources, each instances returns all resources when it exits.
I agree with that statement, but you assume that
Bob Smith wrote:
Peter Hansen wrote:
How have
you proven that it is not *that* program which is at fault?)
It would surprise me: even if it consumes much CPU-time, memory and
other resources, each instances returns all resources when it exits.
I have not. All I know is that on WinXP, the program
Bob Smith wrote:
Peter Hansen wrote:
[snip details of Bob's platform]
WinXP Home, Service Pack 2, AMD 1400MHz proc, 256MB Ram
That's not really much RAM for a WinXP box. Do you have
lots of physical memory available before running?
(I presume you're using a version of nmap that's compiled
for Wind
Peter Hansen wrote:
Bob Smith wrote:
Attached is the code. Run it yourself and see. You too Peter. Be
gentle with me, this was my first attempt with threads.
Thanks, Bob, and I will, but not before you answer some of my
questions.
I had good reasons to ask them, one of which is that I don't
feel
Bob Smith wrote:
Attached is the code. Run it yourself and see. You too Peter. Be gentle
with me, this was my first attempt with threads.
Thanks, Bob, and I will, but not before you answer some of my
questions.
I had good reasons to ask them, one of which is that I don't
feel like wasting my time
On Sat, 08 Jan 2005 15:00:05 -0500, Steve Holden <[EMAIL PROTECTED]>
wrote:
>> Does the Win32 port of Python have a memory leak? I have some code that
>> runs flawlessly on Linux, but bombs after a few hours on Windows. It's
>> threaded and uses a lot of memory.
>Yes, that's a well-known proble
Steve Holden wrote:
Bob Smith wrote:
Does the Win32 port of Python have a memory leak? I have some code
that runs flawlessly on Linux, but bombs after a few hours on Windows.
It's threaded and uses a lot of memory.
Thanks!
Yes, that's a well-known problem. Code that runs with a few errors will
Bob Smith wrote:
Does the Win32 port of Python have a memory leak? I have some code that
runs flawlessly on Linux, but bombs after a few hours on Windows. It's
threaded and uses a lot of memory.
Thanks!
Yes, that's a well-known problem. Code that runs with a few errors will
port without any tro
Bob Smith wrote:
Does the Win32 port of Python have a memory leak? I have some code that
runs flawlessly on Linux, but bombs after a few hours on Windows. It's
threaded and uses a lot of memory.
Let's see what you're missing:
1. platform specifics
2. versions of things involved
3. any sort of det
Does the Win32 port of Python have a memory leak? I have some code that
runs flawlessly on Linux, but bombs after a few hours on Windows. It's
threaded and uses a lot of memory.
Thanks!
--
http://mail.python.org/mailman/listinfo/python-list
13 matches
Mail list logo
