Hi
can anyone see what wrong with
exec_dset("/path/to/program.php") unless of course exec_dset only likes shell scripts
Iqbal
A quick guess would be that unless your system knows that .php files are to be executed by the php interpreter and the interpreter is automatically called, you're going to have to find a way to issue something like "php /path/to/program.php". PHP code is "NOT" directly executable, it is interpreted.
Regards, Norm
Iqbal wrote:
Hi
can anyone see what wrong with
exec_dset("/path/to/program.php") unless of course exec_dset only likes shell scripts
Iqbal
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
I can run the script direct from the command line, but I did try what you suggested, but still no luck it still says syntax error.
iqbal
Norman Brandinger wrote:
A quick guess would be that unless your system knows that .php files are to be executed by the php interpreter and the interpreter is automatically called, you're going to have to find a way to issue something like "php /path/to/program.php". PHP code is "NOT" directly executable, it is interpreted.
Regards, Norm
Iqbal wrote:
Hi
can anyone see what wrong with
exec_dset("/path/to/program.php") unless of course exec_dset only likes shell scripts
Iqbal
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
.
Here's another suggestion. Note that I have not used exec_dset() to try to execute PHP.
Place a call to the php interpreter on the first line of your PHP file as noted below. If it works for you great, if not, someone else might need to assist.
#!/usr/local/bin/php -q <?php echo "Hello, World!\n"; ?>
Regards, Norm
Iqbal wrote:
I can run the script direct from the command line, but I did try what you suggested, but still no luck it still says syntax error.
iqbal
Norman Brandinger wrote:
A quick guess would be that unless your system knows that .php files are to be executed by the php interpreter and the interpreter is automatically called, you're going to have to find a way to issue something like "php /path/to/program.php". PHP code is "NOT" directly executable, it is interpreted.
Regards, Norm
Iqbal wrote:
Hi
can anyone see what wrong with
exec_dset("/path/to/program.php") unless of course exec_dset only likes shell scripts
Iqbal
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
.
In case anyone wants a laugh....well I was using exec_dset{"/path/to/program.php") as opposed to exec_dset("/path/to/program.php")...see if you can spot it
Iqbal
Norman Brandinger wrote:
A quick guess would be that unless your system knows that .php files are to be executed by the php interpreter and the interpreter is automatically called, you're going to have to find a way to issue something like "php /path/to/program.php". PHP code is "NOT" directly executable, it is interpreted.
Regards, Norm
Iqbal wrote:
Hi
can anyone see what wrong with
exec_dset("/path/to/program.php") unless of course exec_dset only likes shell scripts
Iqbal
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
.
:) it happens ;)
regards, bogdan
Iqbal wrote:
In case anyone wants a laugh....well I was using exec_dset{"/path/to/program.php") as opposed to exec_dset("/path/to/program.php")...see if you can spot it
Iqbal
Norman Brandinger wrote:
A quick guess would be that unless your system knows that .php files are to be executed by the php interpreter and the interpreter is automatically called, you're going to have to find a way to issue something like "php /path/to/program.php". PHP code is "NOT" directly executable, it is interpreted.
Regards, Norm
Iqbal wrote:
Hi
can anyone see what wrong with
exec_dset("/path/to/program.php") unless of course exec_dset only likes shell scripts
Iqbal
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
.
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
-
Bogdan-Andrei Iancu -
Iqbal -
Norman Brandinger