Saturday 19 April 2008 10:09:13 am
Hi I have done that using the cron job to call /usr/bin/php -i and I get all of the info including:
Configuration File (php.ini) Path => /etc/php.ini
Scan this dir for additional .ini files => /etc/php.d
additional .ini files parsed => /etc/php.d/dom.ini,
/etc/php.d/gd.ini,
/etc/php.d/imap.ini,
/etc/php.d/mbstring.ini,
/etc/php.d/mysql.ini,
/etc/php.d/mysqli.ini,
/etc/php.d/pdo.ini,
/etc/php.d/pdo_mysql.ini,
/etc/php.d/pdo_sqlite.ini,
/etc/php.d/xmlreader.ini,
/etc/php.d/xmlwriter.ini, /etc/php.d/xsl.ini open_basedir => no value => no value
safe_mode => Off => Off
safe_mode_exec_dir => no value => no value
safe_mode_gid => Off => Off safe_mode_include_dir => no value => no value This must be getting its settings from the /etc/php.ini since when I set safe mode to off in there the cron job picks it up as being off. Also I did discover one strange thing that may help fix this: when I login using SSH and type /usr/bin/php (pathtoeZ)/runcronjobs.php I get the same "No database handler" error message on the command line. BUT if I then type cd (pathtoeZ) and THEN from there type exactly the same command in it works! So it must be that the cron job is running it from the same place where it can't find the database handler, but (even though I put the full path both times) when run from inside the eZ folder the same command works. Really strange... Do you know why this should be? Thanks!
|