ID: 50503 Updated by: paj...@php.net Reported By: tidustracker at freenet dot de -Status: No Feedback +Status: Assigned Bug Type: Program Execution Operating System: Windows Vista PHP Version: 5.3.1 -Assigned To: +Assigned To: pajoye New Comment:
Will take a look early in January for 5.3.2 Previous Comments: ------------------------------------------------------------------------ [2009-12-25 01:00:00] php-bugs at lists dot php dot net No feedback was provided for this bug for over a week, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open". ------------------------------------------------------------------------ [2009-12-19 13:23:52] carsten_sttgt at gmx dot de > but that's not a proc_open bug then. Correct, but I think it there a basic problem with proc_open on Windows. In this case with the environment. Just see this example: http://de.php.net/manual/en/function.proc-open.php#function.proc-open.examples It's not working on Windows (returning 1 and no output). If you change: - $process = proc_open('php', $descriptorspec, $pipes, $cwd, $env); + $process = proc_open('php', $descriptorspec, $pipes); it's "working". But also no output, because the environment $_ENV is empty (even the new process should inherit the current ENV). if you now change: - write($pipes[0], '<?php print_r($_ENV); ?>'); + write($pipes[0], '<?php print_r($_SERVER); ?>'); you can see there is an output. But as long $env is an array (and not null) the script is not working). And so it's also not possible to define new env variables for the new process. Regards, Carsten ------------------------------------------------------------------------ [2009-12-17 01:31:51] paj...@php.net but that's not a proc_open bug then. PHP has no idea about what has called it. I'm not sure either why they are not defined in this case. ------------------------------------------------------------------------ [2009-12-17 01:22:23] tidustracker at freenet dot de The script is working very well? Adjust the two paths and run it in CLI. The ENVs are not the problem, the ENVs cause the problem. The php example code starts via proc_open a new php process. With an passed $env array to proc_open, the two constants SOL_TCP and SOL_UDP described at http://php.net/manual/en/sockets.constants.php are missing in the new php process. ------------------------------------------------------------------------ [2009-12-17 01:01:51] paj...@php.net Please provide a valid/working script. The easiest way to verify that all ENVs are correctly defined is to simply echo them out (echo %ENVNAME%). ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/50503 -- Edit this bug report at http://bugs.php.net/?id=50503&edit=1
