On Fri, 16 Apr 2004, J.J.Green wrote:

> > > Im having a bit of a problem with an application Ive written, which
> > > occasionally fails with an "FTP response reading failed" from
> > > curl_easy_perform().
> >
> > And the server are providing a nice and clean FTP command response?
>
> Of course! but to syslog :-)
>
> It's a daemon sending data to clients, when I get nonzero return from
> curl_easy_perform() I just mark the job as not-sent and put it back in the
> queue to try again later.

What I mean with "nice and clean FTP command response" is a protocol-compliant
answer to a previous FTP command sent by curl. The error message "FTP response
reading failed" means that curl failed while reading such a response from the
server.

So, if the server speaks fine FTP when this happens, it is a curl bug to say
this. If the server didn't respond with a nice response, then the error is no
longer a mystery.

> I should have said : this is Debain linux 2.4.22 , gcc-3.3, curl 7.11.1
> (debian libcurl2 v 7.11.1-1). The manual for sendmsg(2) mentions
> MSG_NOSIGNAL, so I think that this a supported platform

Yes. There shouldn't be any SIGPIPEs for you...

-- 
     Daniel Stenberg -- http://curl.haxx.se -- http://daniel.haxx.se
      Dedicated custom curl help for hire: http://haxx.se/curl.html