[PHP Guru question]: run php script from within pecl extension

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

At this point I think one starts wondering whether PHP is the correct
tool for the job...

Jasper

Roland Schwingel wrote:

Hi...

For several reasons I need to call a php script every x minutes.
I need that on several platforms so I started to write a pecl
extension that implements something like a cron service.

I am running my php 5.1.5 always together with apache 2.2.3.
So I made a small pecl that spawns a thread using apache apr functions.

In this thread I want to call a php script, so I do this whenever
the time to execute the script is reached:

TSRMLS_FETCH();

zend_file_handle zfd;

zfd.type = ZEND_HANDLE_FILENAME;
zfd.filename = <absolute path to php script to execute>
zfd.free_filename = 0;
zfd.opened_path = NULL;

php_execute_script(&zfd TSRMLS_CC);

Obviously I miss something in initing php, because php
crashes in main/streams/streams.c function
php_stream_locate_url_wrapper() when I call php_execute_script()

because the variable
'wrapper_hash' inited at the very beginning in that
function appears to become a bad value.

So I hope someone here can help me or give me some pointers
to get help...

Thanks in advance,

Roland

Jasper Bryant-Greene
Director
Album Limited

jasper@album.co.nz
+64 21 708 334 / 0800 425 286
http://www.album.co.nz/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5-ecc0.1.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iFcDBQFFG4F8nqZ4vwo6v1gRCjTcAQCYxarnzuhCEyxO5q1AzRQp9Cfu/d3ob22p
/v4OuCnqVQEAnXx/1xYi7awcDtQ2iCS7/a16RHggUyKLStuB/5ZydWQ=
=VNlE
-----END PGP SIGNATURE

For several reasons I need to call a php script every x minutes.
I need that on several platforms so I started to write a pecl
extension that implements something like a cron service.

Why not cron then?

Obviously I miss something in initing php, because php
crashes in main/streams/streams.c function php_stream_locate_url_wrapper()
when I call php_execute_script()

Correct. You're not in a request (you're probably not even in an
identifiable/unique thread context). Both are fixable by spinning up a
context at thread startup and either (A) wrapping a request
activate/deactivate around that timer, or (B) wrapping the
activate/deactivate just inside your thread context (giving you a
single-uberlong-running request).

because the variable
'wrapper_hash' inited at the very beginning in that
function appears to become a bad value.

Which tells me that both of the issues above are relevant.

But coming back to the first question: What's wrong with cron?

-Sara