Ben Greear wrote:

> The application is forked & exec'd, the stderr and stdout is redirected to
> a file by the script that starts the main app.
> I definately see stdout messages from my own code, but not sure about
> stderr.
>
> I'll try the CURLOPT_STDERR first thing tomorrow and let you know
> what I see.

I think I am doing something wrong. Currently, I'm using curl_easy_perform.
I have several call backs, and some signal handlers. To stop the process I
send it SIGQUIT, which will set a flag that causes the callback to call
curl_easy_cleanup, among other things.

I was thinking that this would automatically cause the curl_easy_perform to
return, but now I think that instead I am cleaning up it's memory when it
is still trying to use it.

Is there some way to gracefully cause curl_easy_perform() to stop what it's
doing and return immediately?

If not, I can just kill the process with kill SIGKILL or call exit() in the
callback instead of trying to gracefully clean up....

Thanks,
Ben

-- 
Ben Greear <greearb_at_candelatech.com>
Candela Technologies Inc  http://www.candelatech.com