go to bug id or search bugs for
Currently, any child process started from PHP using popen(), proc_open() or exec() etc. will inherit opened file handles. This is caused by TRUE value of the bInheritHandles parameter of the CreateProcess WinAPI function.
This lead to the following issue. Example pseudocode:
$f = fopen('file.txt');
If you will try to run these scripts you will get the exception on unlink('file.txt') line saying you don't have such permissions to remove the file. Because the opened file handle was inherited by the child process 'php worker.php' and even if you fclose() the starter's file handle the file can not be deleted while there is any other handle referenced to it in any other process in the system.
So in this case the worker process do nothing in its code to lock the file, but system internals do it and the script can not prevent it.
So I suggest to add an ability to set the bInheritHandles flag to FALSE when creating child processes to prevent the issue when child process keeps file handles implicitly.
The file.txt shold be deleted by the unlink() function.
unlink() function fail to delete file.txt with message of lack permissions.
Add a Patch
Add a Pull Request
popen is supposed to behave like a fork. The Windows behavior mirrors the Unix behavior.
Maybe you should be using proc_open?
I tried the proc_open() function but it has the same issue - file handles are inherited from the parent process. So all files opened in the parent process at the time of the child process starting remain opened all the time while child process is running. This is an important issue if child process should work much longer than parent process.
This issue appears on both Windows and Unix as it seems. It causes https://github.com/amphp/aerys/issues/192 and without a fix it's not possible to launch long-running child processes in any long running PHP script like an app server.
See the 'e' mode flag for fopen.
Will the 'e' fopen flag work under Windows?
The 'e' flag doesn't work on Windows, works only for fopen and I don't know any library that uses it, so it doesn't really help.
I think the default should be changed to use O_CLOEXEC. Another alternative is to just close all descriptors after the fork and before the exec that are not 0|1|2, at least with an option such as "inherit_handles" => false.
On Windows it's trivial to implement "inherit_handles" => false, because it's explicitly set there.