On Sat, 9 Jun 2007, Alessandro Vesely wrote:

> A couple of days ago, a few dozens of files did not pass from one client.

[...]

> The problem is on the client, because it only happened on that PC. In facts,
> the poor machine had a huge amount of opened handles and was working badly.
> Our best bet is that curl encountered a critical error and was terminated.

In other words: you have no idea what happened, and a very far-fetched
long-shot guess is this?

Why not just enable more logging and check carefully exactly what happened and
then try to attack and fix the actual error?

> Because the calling batch is called from a service, it was not interactive.
> Perhaps, if it were interactive it could have shown a message like
>
> "The application failed to initialize properly (0xC0000017).
> Click OK to terminate the application."

No, curl never displays anything like that. If it fails internally, it returns
an error back and displays an error message. Which should be enough for every
script/batch file to show and/or catch.

-- 
  Commercial curl and libcurl Technical Support: http://haxx.se/curl.html