If you run
php test3.php &
Runs, gives a process ID, etc. No errors being eaten by /dev/null on the
screen or any log file for example.
If you modify test2.php so any errors are easily visible,
change
exec("php test3.php &> /dev/null &");
to
exec("php test3.php &");
Run test2.php again, the problem is still there. Even with correct
default shell (in case it wasn't for some reason), the problem still
persist.
So while it would be great if the error was a simple as a default shell
command mismatch, so far there appears to be no evidence to support
this. So I am confused if this is a php-cli issue or not, but so far all
evidence points to it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1265983
Title:
php5 cli one instance/process limit
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1265983/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
