drifter Posted December 8, 2006 Share Posted December 8, 2006 I am writing some really big jobs for cron that will sometimes take hours to run. I test them in a browser not as cron.I do not want a lot of out put because I need to log the result or get them emailed to me. (who needs 1,000,000 sucessfull statements.)Anyway, I have notice if I do not print much data, the browsers seem to just stop responding in a few minutes. IE and Mozilla. I do have a set_time_out(0);If I echo enough data to make it flush by itself, or I occasionally do an ob_flush();flush(); - the script will run for hours.So is this a browser related issue? will I not have these problems as cron? Is this s php.ini setting of some type? Link to comment https://forums.phpfreaks.com/topic/29984-bowser-timing-out/ Share on other sites More sharing options...
roopurt18 Posted December 8, 2006 Share Posted December 8, 2006 Even though you set the time out to 0, I believe that has no bearing on database interactions. Do you have access to a CLI so you can test your cron jobs that way? It will make your life a little easier. Link to comment https://forums.phpfreaks.com/topic/29984-bowser-timing-out/#findComment-137783 Share on other sites More sharing options...
linuxdream Posted December 9, 2006 Share Posted December 9, 2006 Check your logs for warning about set_time_out. If safe_mode is on, then set_time_out doesn't work and it only tell you this in the logs not in the browser. I've had this happen and it was frustrating as heck. Might help. Link to comment https://forums.phpfreaks.com/topic/29984-bowser-timing-out/#findComment-137982 Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.