> I'm guessing it's just a timeout issue - "maximum execution time > exceeded" type thing - check your php or apache error logs and see > what that tells you.. if nothing shows up, turn log_errors on, restart > apache and see what you get. I don't think it's a timeout issue on the server-side, because I've already tried setting MAX_EXECUTION_TIME and MAX_INPUT_TIME to extremly high values, and got the same result (i.e. the blank page). By setting them to extremly low values I was able to verify the app/script/server 's behaviour when it did timeout, and that produced the expected warning-message for MAX_EXECUTION_TIME exceeded.
A browser has a timeout too.. type about:config in firefox, look for network.http.connect.timeout - timeout is 30 seconds and network.http.request.timeout is 120 seconds... thats not a long time.
I couldn't find anything in the logs, although log_errors is turned on, and the logging levels set to log everything thats possible. > > Try adding some flush() calls to the script. That might get the > browser to display some content.. Don't know whether it will work though. That's something I haven't tried yet, so thanks for the tip. > > Copy has to wait until it's finished before telling you the results. > If it's copying a 20M file, that takes a while.. If you're copying > multiple 20M files, then hey.. there's you're problem. How many and > how big are the files in this case? We're talking about multiple copy operations. The first one copies 230 files (approx. 40mb) and the second one copies about 2200 files (195mb). Most files are under 400kb a piece.
Time how long it takes you to manually copy that amount of data.
> You might be better off running a script to run through cron every 5 > minutes or so and doing it all for you.. then getting it to email you > the results. > Running the script through cron wouldn't be a good idea. The app we're talking about is a kind of Content Management System for photographers, so the publish-request should only be called when the user has finished his modifications to the site and is ready to publish them to his website.
The request goes in to a "process" queue with the relevant details.. obviously this only gets logged right at the end. Cron job runs, finds the details, does its work.. If you're trying to do all of this in one step I think you're out of luck and you might need to break up the processes. -- Postgresql & php tutorials http://www.designmagick.com/ -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
