Search results

Relevant to the topic, this is Redhats page on how they backport security fixes. This would apply to Centos as well https://access.redhat.com/security/updates/backporting

It shouldnt be an issue now, that problem was resolved in the last release

This is why the LSB uses /var/log/httpd, logrotate is already set up to do that for every log file that drops into that directory. Additionally you would not associate a logrotate config with an apache module, since a module does not restart apache (and should not to avoid multiple restarts)...

And then you installed it with yum right? yum install php-panda

thatd be it then, run the installer again without the -q flag.

Did it actually add the repo? Should be called atomic.repo on the system

Crazy easy. It installs the php versions into an alternate location so it wont conflict with the distro build, adds a drop down selector into plesk for each domain so your users can select what they want to use. Updates are over the regular yum mechanism.

You can add it to plesk right now with PHP Panda: http://talk.plesk.com/threads/php-panda-multi-php-installer-for-plesk.293750/

Updated to: PHP 5.6.7 PHP 5.5.23 PHP 5.3.39 Changes: Fixed the php-fpm.conf from atomic-php54-php-fpm reported above. Thanks for the report!

PHP Panda could certainly be used in this context, both the cgi/fcgi and dso module are available in the install. I believe there was one thread in the atomic forums about using it in a DSO context via the SCL system.

We favor sticking with the LSB guidelines, where the audit logs will be in the same directory as the rest of the httpd logs: /var/log/httpd/

So you'd probably want to remove that source install first if you're installing PHP Panda on the same system. At the very least, you'd have less confusing output. Worst case you could be causing the two named php versions to collide.

Added latest versions: * PHP 5.6.6 * PHP 5.5.22 * PHP 5.4.38 Release Notes: - Fixes CVE-2015-0235 (5.4, 5.5, 5.6) - Fixes CVE-2015-0273 (5.4, 5.5, 5.6)

@DaveK there are updates for mysql 5.5 in the atomic repo, but it is not required. If you do want to upgrade to 5.5, you'd need to remove the mysqlclient18 first.

It depends on if you want to run Mysql 5.5 or not. You'd need to decide on one or the other

An alternative are to use the mult-version php packages from here: http://talk.plesk.com/threads/php-panda-multi-php-installer-for-plesk.293750/

Upgrades to PHP 5.4 are available from the atomic repo, as well as the Multi-PHP project: http://talk.plesk.com/threads/php-panda-multi-php-installer-for-plesk.293750/page-10#post-774181

Thats just a string in a table. Check your versions with the rpm command. If you dont have the latest, you can always upgrade it with yum. I'll look into the 5.5 thing. Could be its trying to talk to a fcgi daemon that isnt there

This is more of a planning question, are there any specific 3rd party modules you'd like to see added to PHP Panda by default? I know some commercial ones have been discussed here already, like ioncube and zendguard, is there anything else we should have on the radar?

Selinux enabled? Or is maybe the tun kernel module isnt loaded?