On Thu, 22 May 2003, Cadime wrote:

> I am doing several NLST to an FTP server that replies with a "550 No files
> found" I think this is not a valid answer, right?

Nope, not according to RFC959 section 5.4. But libcurl isn't that picky. If
it doesn't get the "OK" message it treats the rest as bad ones.

> Anyway, in this case, as I am trying to re-use connections, I was able to
> see that sockets were not closed and I run out of file handles, after a
> while...

Could you please provide us a with a full source code example of a program
showing when this happens? Preferably against a public URL, or if not else
with a bit of a debug dump so that we can see how the server of yours
responds to your program.

> I was not able to compile my code as in README.memoryleak (HPUX ???)

Why not? What happens? The memory debug system should work on unix systems.

> I am not an expert on CURL, either...

The bright side of the built-in memory debug system is that once you can
build and use it, it points out the offender for you, no need to understand
anything! ;-)

-- 
 Daniel Stenberg -- curl: been grokking URLs since 1998
-------------------------------------------------------
This SF.net email is sponsored by: ObjectStore.
If flattening out C++ or Java code to make your application fit in a
relational database is painful, don't do it! Check out ObjectStore.
Now part of Progress Software. http://www.objectstore.net/sourceforge