Hot answers tagged php
Your PHP interpreter is set to terminate any script which requires more than 132MB of memory. Your script is trying to allocate more than 161MB of memory. The problem is quite simple, and so are the solutions. You can either: Get your PHP interpreter to allocate more. The reason why your host is advising against that is that if he didn't, he'd end up ...
Post your texts from directory: /etc/apt/sources.list to see if the repository list would suffice or not. See the link, this may be worth seeing.
Ok, here it is answered by pierre schmitz, thx nymous for the link: openssl, phar and posix modules are now built in php7 core. Remove the corresponding directives from your php.ini, e.g. ;extension=openssl.so. php-xcache is incompatible with php7, remove package, the project seems dead. full list of 3rd party package status: | Package | Status ...
I used to solve exactly this problem for my game servers by writing a perl daemon that owned and controlled gameservers, and answered ad a web service to outer world. Simply put, but effective.
When you access the web-page (PHP script), the content is sent by one instance (sub-process) of the httpd server process. When you restart the httpd server, the script is informing the server to die, which will kill all the sub-processes too, including the PHP instance running the script itself. Basically the script is effectively committing suicide. Try ...
Only top voted, non community-wiki answers of a minimum length are eligible