as I said, the default timout is 300 seconds, a lot longer than my program
takes to run, and I am pretty certain that if timeout were triggered, I'd
see it in the client.
Yeah, I'm using a browser on the php page, and everything seems to
function fine from the browser to the server, it's after the server gets
the uploaded file and begins to play with it that things become weird.
On
Wed, 21 Sep 2005, John Nichel wrote:
ernst@xxxxxxxxxxxxxxx wrote:
timeout isn't being used on either of these machines, and as far as I read
it, the timeout directive would make the web server fail, producing an
apache error or some strange behaviour on the client end. Neither of
How is timeout _not_ being used? It's a core directive. If the timeout is
reached, the thread dies, along with anything running with it.
these happens, the php script completes normally, but the exec command (and
only these exec commands, I'm using others in the script that work fine)
doesn't always complete. Even if timeout was set to its normal default of
300 seconds, this all happens way before 300 seconds have passed. The
whole process takes about 20 or 30 seconds.
Just to make sure I'm understanding you, you're hitting the php page in a
browser, right? Like you're going to http://www.yourhost.com/page.php where
page.php contains somthing like...
<?php
exec ( '/path/myapp', $out, $res );
?>
Right?
--
John C. Nichel
ÜberGeek
KegWorks.com
716.856.9675
john@xxxxxxxxxxxx
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
New Disorder Records - ten years of something:
Coming soon, new Power Struggle CD.
* Free Email with 5 megs, no ads
* Internet Radio Station - upload your music, we'll put it in rotation
* 100's of CDs for sale
* videos, message board, byofl
http://www.newdisorder.com
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
