search for: phpm

...e for me > > and what says "php -m" or "rpm -qa | grep php"? On CentOS 5 php-5.1.6-39.el5_8 php-cli-5.1.6-39.el5_8 php-common-5.1.6-39.el5_8 php-devel-5.1.6-39.el5_8 php-gd-5.1.6-39.el5_8 php-ldap-5.1.6-39.el5_8 php-mbstring-5.1.6-39.el5_8 php-mcrypt-5.1.6-15.el5.centos.1 phpmyadmin-2.11.11.3-2.el5.rf php-mysql-5.1.6-39.el5_8 php-pdo-5.1.6-39.el5_8 php-pgsql-5.1.6-39.el5_8 On CentOS 6 php-5.3.3-22.el6.x86_64 php-cli-5.3.3-22.el6.x86_64 php-common-5.3.3-22.el6.x86_64 php-enchant-5.3.3-22.el6.x86_64 php-gd-5.3.3-22.el6.x86_64 php-IDNA_Convert-0.8.0-1.el6.noarch php-ldap-...

Greetings, A malfunctioning disk this past week accelerated a lingering decision to move to CentOS 6.x from CentOS 5.x. Most of our content is functioning and being presented as it should be. However, there appear to be php-related issues. Basic squirrelmail (a php-dependent package) works correctly. However, drupal, and other php-dependent parts that call postgresql and mysql databases of

It appears to be a low-level attack, not so frequent as to be banned permanently, just a number of times a day. I did google on this, and I gather it's looking for phpmyadmin. We've been getting one from one specific network in Russia for weeks Here are more information about 91.201.64.24: [Querying whois.ripe.net] [whois.ripe.net] <snip> % Information related to '91.201.64.0 - 91.201.67.255' inetnum: 91.201.64.0 - 91.201.67.255 netnam...