如果Pcntl_fork开启了安全模式，它将无法在web服务器环境中工作。在这种情况下，它只能在CLI版本的PHP中工作。

如果Pcntl_fork开启了安全模式，它将无法在web服务器环境中工作。在这种情况下，它只能在CLI版本的PHP中工作。

您可以模拟线程。PHP可以通过popen(或proc_open)运行后台进程。这些进程可以通过stdin和stdout进行通信。当然，这些进程本身也可以是一个php程序。这可能是你能找到的最接近的了。

您可以使用exec()来运行命令行脚本(例如命令行php)，如果您将输出管道到一个文件，那么您的脚本将不会等待命令完成。

我不太记得php CLI的语法，但你会想要这样的东西:

exec("/path/to/php -f '/path/to/file.php' | '/path/to/output.txt'");

我认为相当多的共享托管服务器出于安全原因默认禁用了exec()，但可能值得一试。

您可以选择:

multi_curl 可以使用系统命令来实现相同的功能 理想的情况是，用C语言创建一个线程函数，然后用PHP编译/配置。这个函数是PHP的函数。

As of the writing of my current comment, I don't know about the PHP threads. I came to look for the answer here myself, but one workaround is that the PHP program that receives the request from the web server delegates the whole answer formulation to a console application that stores its output, the answer to the request, to a binary file and the PHP program that launched the console application returns that binary file byte-by-byte as the answer to the received request. The console application can be written in any programming language that runs on the server, including those that have proper threading support, including C++ programs that use OpenMP.

一个不可靠的，肮脏的技巧是使用PHP来执行控制台应用程序，"uname"，

uname -a

and print the output of that console command to the HTML output to find out the exact version of the server software. Then install the exact same version of the software to a VirtualBox instance, compile/assemble whatever fully self-contained, preferably static, binaries that one wants and then upload those to the server. From that point onwards the PHP application can use those binaries in the role of the console application that has proper multi-threading. It's a dirty, unreliable, workaround to a situation, when the server administrator has not installed all needed programming language implementations to the server. The thing to watch out for is that at every request that the PHP application receives the console application(s) terminates/exit/get_killed.

As to what the hosting service administrators think of such server usage patterns, I guess it boils down to culture. In Northern Europe the service provider HAS TO DELIVER WHAT WAS ADVERTISED and if execution of console commands was allowed and uploading of non-malware files was allowed and the service provider has a right to kill any server process after a few minutes or even after 30 seconds, then the hosting service administrators lack any arguments for forming a proper complaint. In United States and Western Europe the situation/culture is very different and I believe that there's a great chance that in U.S. and/or Western Europe the hosting service provider will refuse to serve hosting service clients that use the above described trick. That's just my guess, given my personal experience with U.S. hosting services and given what I have heard from others about Western European hosting services. As of the writing of my current comment(2018_09_01) I do not know anything about the cultural norms of the Southern-European hosting service providers, Southern-European network administrators.