On Wed, 20 Jun 2001, Shawn Poulson wrote:

> I have a script in Perl now that manages many curl processes (via
> Win32::Process) to download several files. This works great, however, I'm
> finding that curl aborts several times at random with the error message
> "(23) Failed writing body". There is over 300G free on the drive I write
> to. If it matters I am using a UNC path to a remote server for file
> storage.

I'm afraid I don't know what a "UNC path" is. I do know what that error
message means though: it means that the write somehow failed. It returned an
error in the Curl_client_write() function (source line lib/sendf.c line 229
in my copy).

This is not really curl's fault. If you used the curl command line tool
(which I guess you did), that was a 'fwrite()' call that failed. The fwrite
function is then part of the C library/DLL.

> Unfortunately curl is not able to resume broken downloads when connecting
> to an IIS 4.0 FTP server.

I don't see how that is a flaw in curl though. Can you? If so, can you show
us a failed resumed download (with -v)?

> As a test, I have run plain FTP and curl side-by-side storing files to
> the same remote directory via mapped drive (since FTP can't handle UNC).
> I have seen curl abort a couple times where FTP just keeps on going. NT
> Performance Monitor verifies this activity.  Any ideas?

I'm sorry to admit that I have no ideas at all. There's nothing magic in what
curl does to download files. It is the same download logic that runs on _all_
platforms that curl is built and run on.

I would need a lot of more details to understand why curl stops (or perhaps,
why the ftp client doesn't).

-- 
     Daniel Stenberg -- curl dude -- http://curl.haxx.se/
_______________________________________________
Curl-library mailing list
http://curl.haxx.se/libcurl/