That doesn't sound like the problem, but you can either view the
/var/log/messages log to see if it is leaking as the kernel will be the
first to complain.

If you have the time I also recommending opening a few terminal windows
and running:

Tail -f /var/log/messages (watch the kernel)
Tail -f /var/log/cron (watch cron)

Then run that script and see what's going on. Between this and the
logging let us know what the error is and we'll see.

Hope this helps,

Justin S.

-----Original Message-----
From: curl-and-php-bounces_at_cool.haxx.se
[mailto:curl-and-php-bounces_at_cool.haxx.se] On Behalf Of John Wards
Sent: Sunday, October 24, 2004 7:47 AM
To: Programming PHP/CURL
Subject: RE: Curl seg fault...i think..

Quoting Justin Seitz <justin.seitz_at_shaw.ca>:
> You can still use curl_error() and curl_errno() within a command line
> script. If you are running it in cron and it's dying, then do
> something like this:
>
> Curl_exec($ch) or die (system("cat ".curl_error($ch)." >>
> error.txt"));
>
> When your cron job hits that curl_exec it will kick the error into
> error.txt, depending on your system you may have to run:
>
> Sh$ touch error.txt
>

Thanks, I'm uploading that just now and will run the script.

It took 40 minute to die the last time (its compleatly random...) so
we'll see...I bet it runs fine this time.

Oh I notice that 7.12.2 is out but freebsd have yet to release a port
for it (its only been 6 days I suppose ;-)) it wouldn't be anythign in
7.12.1 would it? I think i get time based cookies (that was the only
thing I noticed from the change log) would a mem leak cause a seg fault?

John

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
Received on 2004-10-24