Rodolfo De Nadai wrote:
Edward , my best guess is that not IE is holding the connection but the
apache user... because the process is related to the apache user... and
there's more i can close IE, bacause i use the directive 2> log.log & on
the call of system.
Example:
system("php myscript.php 2> log.log &");
This why IE will not wait until the script is finish...
One thing i can't understand is why this child process of the apache
user is not killed when i restart apache... that's the real deal...
thanks
This doesn't actually start a new process of PHP seperate from Apache. What you are doing is
starting a child process of the child process or the root process of Apache.
What you might want to look in to is http://us2.php.net/manual/en/ref.pcntl.php
This will help you fork your processes, but I think you are still going to run into the same problem
even if you fork it within the php process of apache.
What you are probably going to need to do is create your own custom script that will act as a
daemon, and replace apache altogether.
This way it is completely separate from apache. It can run on its own port and
only answer to you.
--
Jim Lucas
"Some men are born to greatness, some achieve greatness,
and some have greatness thrust upon them."
Twelfth Night, Act II, Scene V
by William Shakespeare
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
