yes, i've already come across the problem of timeout. most systems are set to 30 seconds. i used ini_set("max_execution_time", "60") to fix it.
Still not really a good answer, perhaps splitting it up into several seperate scripts would be better; if it's taking that long to run, that's way too long imo...
you mean, call php from the command line, called from cronjob?
php < code.php
i can't seem to bring php up like this ... (unix is not really my forte).
No, more setting a cron task to execute: php /path/to/code.php
well, if you show me yours, i'll show you mine
actually, it's nothing too special. just a lot of data munging to extract data from particular locations within tables.
and a few data cleanup routines to put the information in a useable format.
i'm not sure it would be of generic interest.
Which one did you want to see? lol...
As for using exec or system, some isp's block them out, if you where to execute them from command line you could have them run fine in the back end of things, cron would execute them on a set schedual and you wouldn't have to worry about any potention forum lag.
BTW, you may not notice any lag now, but trust me, you will lol...
