http://forum.swsoft.com/showthread.php?t=38404&highlight=chroot 1.) MySQL Access Rights On your Plesk server: Create a MySQL user eg.: secondarydns Using phpmyadmin, grant this user the SELECT option only for the table domains of the psa database. Also for maximum security you should set the hostname from which this user will logon.
I’ve recently been doing the exact same thing (albeit 32-bit), having previously always used Fedora, so I thought I’d give you a ‘how-to’ based entirely on my experiences (so it’s not neccesarily gospel, but it’s worked fine for me):
Definitely sounds like bind-chroot is the culprit. I’ve had a few problems with it myself. Once you’ve removed it from your machine Quote: yum remove bind-chroot service named start add the following line to your yum.conf file under the [main] section Quote: exclude=bind-chroot
php.ini error_reporting = E_ALL display_errors = on Για καλύτερη προστασία από επιθέσεις καλό είναι το display_errors να είναι “OFF” find php.ini path http://www.prosoxi.gr/2008/07/04/plesk-phpini/
Comand HTTPD -service httpd status ComandNAMED -service named status ComandQMAIL -service qmail status
Where can I find php.ini configuration file on the Plesk server. APPLIES TO: Plesk for Linux/Unix RESOLUTION Usually php.ini location is /etc/php.ini. And PHP modules *.ini files are placed in /etc/php.d. Also, you can find which configuration files are used by PHP using a script with phpinfo() function: <?php phpinfo(); ?> Open a page which …