I use the popen function to asynchronously execute PHP code {code ...} it turns out that I am in B. php code updates the database (because the logic is too complex, so no account is available .), but only. php executes fread $ open to execute B. php code. if fread is removed, it is not executed. (not in the database... I use the popen function to asynchronously execute PHP code.
// A. php
// B. php
It turns out that I am in B. php code updates the database (because the logic is too complex, so no account is available .), but only. php executes fread $ open to execute B. php code. if fread is removed, it is not executed. (no updates in the database)
Update: It seems that the pclose can be executed normally when it is put far away. it seems that it is the key point time for executing B. php code. if it is disabled early, the execution will be affected. Is this the reason?
Reply content:
I use the popen function to asynchronously execute PHP code.
// A. php
// B. php
It turns out that I am in B. php code updates the database (because the logic is too complex, so no account is available .), but only. php executes fread $ open to execute B. php code. if fread is removed, it is not executed. (no updates in the database)
Update: It seems that the pclose can be executed normally when it is put far away. it seems that it is the key point time for executing B. php code. if it is disabled early, the execution will be affected. Is this the reason?
Try pclose (popen ("php B. php-a $ argv1-B $ argv2 &", 'r '));