Anytime I’ve been running a perl based script on my leopard box I got this really irritating output with whatever else I was expecting:

perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LC_ALL = “En_US”,
LANG = (unset)
are supported and installed on your system.
perl: warning: Falling back to the standard locale (“C”).

With a quick Google search I found an answer. Basically the solution / fix is to make sure the following is set in either your ~/.profile or ~/.bashrc or ~/.cshrc

# This setting is for the new UTF-8 terminal support
export LC_CTYPE=en_US.UTF-8
export LC_ALL=en_US.UTF-8

The first time you use the Perl module CPAN, a script is executed in order to properly configure several options (like the location of tar, gzip and unzip files, the cache size for the build directory, etc).

If you want to modify these configuration options at a later time, you can do it in 2 ways:

- Manually, modifying the configuration files

You can either modify the user-specific file (usually ~/.cpan/CPAN/MyConfig.pm) or the system-wide configuration file (stored somewhere in the perl module directory tree, look for a directory named CPAN that holds a file named Config.pm)

- Automatically, using the CPAN module

To do this, execute the following:

perl -MCPAN -e shell

When you’re in the cpan shell, execute:

cpan> o conf init

UPDATED: January 31st, 2011: Python 2.6 now is in the normal EPEL repositories. There are some changes in the explanations below

I’ve always hated Centos, probably because I’ve never been in a situation where I had to deal with the network security (other than the obvious stuff to ward off cross-site-scripting attacks and the such). Of course, that being the case, I did wind up dealing with CentOS at work and I had to get Django, Python 2.6 and the such functional.

Centos throws a few curveballs your way.. YUM is built on Python 2.4, and upgrading to a newer version supposedly breaks the program. Going back to Python 2.4 was not an option, mainly because all my python experience is on Python 2.5 / 2.6, and I don’t want to go back and learn an older non-maintained version of the language for a server. On the other hand, I didn’t want to lobby to just install Ubuntu.

This assumes you already have a normal LAMP setup. Furthermore, I’m assuming you do not have mod_python installed. This threw me for a loop for the longest time, so take this for what its worth.

The VERY FIRST STEP (if you are running a clean install of CentOS) is to get the dev tools installed.


# sudo yum groupinstall 'Development Tools'


After that, install Python 2.6 (or anything else newer in the 2.x series). As of January 31st, these are in the EPEL repositories; if you don’t have the EPEL repositories enabled, do the following:


# rpm -Uvh http://download.fedora.redhat.com/pub/epel/5/i386/epel-release-5-3.noarch.rpm
# yum repolist


Once that’s done, run yum update to get everything setup, and then install Python & the MySQL dependencies (if they aren’t already installed)


# yum install python26* mysql-devel mysql-server


This installs pretty much everything Python- & MySQL-related that you need. You will need to run the following to get an extra piece of information:


Python 2.6.5 (r265:79063, Apr 16 2010, 13:09:56)
[GCC 4.4.3] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import sys
>>> sys.prefix
'/usr'


The prefix (/usr) is important for later. Set it aside and finish up.


# cd ~
# wget http://sourceforge.net/projects/mysql-python/files/mysql-python/1.2.3/MySQL-python-1.2.3.tar.gz/download
# sudo tar xzvf MySQL-python-1.2.3.tar.gz
# cd MySQL-python-1.2.3*
# python26 setup.py install


(Don’t forget to create a user for use by Django in the database)


# cd ~
# wget http://modwsgi.googlecode.com/files/mod_wsgi-3.3.tar.gz
# sudo tar xzvf mod_wsgi-3.3.tar.gz
# cd mod_wsgi-3.3*
# ./configure --with-python=/usr/bin/python2.6
# make
# make install


Now you need to fix up your Apache configuration. I won’t pretend to be an expert with WSGI (although I’ve managed to get it running on 3 different OSes running Apache), but make sure you include the following, somewhere near the Module block in the httpd.conf file.


WSGIPythonHome /usr/


As long as you have this setup, and a proper WSGI script, you should be able to get up and running.

The Django installation is quite easy. Go into the Django source directory and type in

# python2.6 setup.py install

That will take care of making sure Python2.6 also has access to django.

If you don’t want to install using the source code, you can also do this through pip. Follow the instructions here to install pip (while updating the version of pip to 0.8.2) and then type in

# pip install django

That’s pretty much it. I’m sure there is something unclear, but I’ve got to get back to work -_-

What is LiteSpeed Web Server ?

LiteSpeed Web Server is the leading high-performance, high-scalability web server. It is completely Apache interchangeable so LiteSpeed Web Server can quickly replace a major bottleneck in your existing web delivery platform. With its comprehensive range of features and easy-to-use web administration console, LiteSpeed Web Server can help you conquer the challenges of deploying an effective web serving architecture.

In this tutorial we will upgrade current litespeed PHP to support PHP 5.3.0, Mail header patch and suhosin patch

What is Suhosin ?

Suhosin is the big brother to the Hardened-PHP patch which adds an extra level of protection to PHP.

In this tutorial, i’ve tried to compile all packages from litespeed web server web interface but it’s failed.
so i prefer to configured it manually.

Download All Sources

Login as root

#cd /root
#wget http://uk.php.net/distributions/php-5.3.0.tar.gz
#wget http://download.suhosin.org/suhosin-patch-5.3.0-0.9.8-BETA-1.patch.gz
#wget http://choon.net/opensource/php/php-5.3.0-mail-header.patch
#wget http://www.litespeedtech.com/packages/lsapi/php-litespeed-4.10.tgz
#wget http://ftp.gnu.org/gnu/autoconf/autoconf-2.13.tar.gz

Extract Packages

#cd /root
#tar -zxvf php-5.3.0.tar.gz
#gunzip suhosin-patch-5.3.0-0.9.8-BETA-1.patch.gz
#tar -zxvf autoconf-2.13.tar.gz

Install autoconf

#cd /root
#cd autoconf-2.13
#./configure && make && make install

Compile PHP 5.3.0 with PHP mail header , Suhosin and PHP-Litespeed

#cd /root
#cd php-5.3.0

Patching PHP mail header & Suhosin

#patch -p1 < /root/php-5.3.0-mail-header.patch
#patch -p1 < /root/suhosin-patch-5.3.0-0.9.8-BETA-1.patch

Exctract and Compile PHP-litespeed

#cd /root
#cp php-litespeed-4.10.tgz /root/php-5.3.0/sapi
#tar -zxvf php-litespeed-4.10.tgz
#cd /root/php-5.3.0
#touch ac*
#./buildconf --force

Compile All

#cd /root/php-5.3.0
# ./configure --with-litespeed --prefix=/usr/local/lsws/lsphp5 --with-mysql --with-zlib --with-gd --enable-shmop --enable-track-vars --enable-sockets --enable-sysvsem --enable-sysvshm --enable-magic-quotes --enable-mbstring --with-iconv --with-mcrypt --with-curl --with-ftp --with-gettext --with-ttf --enable-suhosin --enable-gd-native-ttf --with-jpeg-dir=/usr/local/lib --with-freetype-dir=/usr/local/lib --with-kerberos --with-openssl --with-mhash --with-pcre-regex=/usr/local --with-pear --with-png-dir=/usr/local/lib --enable-zip -enable-bcmath --enable-calendar --with-mysqli=/usr/bin/mysql_config
#make

If make is running successfully then stop here.

Copy PHP Binary to litespeed fcgi-bin Directory

#cd /usr/local/lsws/fcgi-bin
#unlink lsphp5
#cp /root/php-5.3.0/sapi/litespeed/php lsphp-5.3.0
#ln -s ./lsphp-5.3.0 lsphp5

Verify PHP Version

#./lsphp5 -v
PHP 5.3.0 with Suhosin-Patch (litespeed) (built: Sep 13 2009 22:29:50)
Copyright (c) 1997-2004 The PHP Group
Zend Engine v2.3.0, Copyright (c) 1998-2009 Zend Technologies

If you see any error like below :

#./lsphp5 -v
PHP Warning: PHP Startup: Unable to load dynamic library ‘/usr/local/lsws/lsphp5/lib/php/extensions/no-debug-non-zts-20090626/suhosin.so’ – Cannot open "/usr/local/lsws/lsphp5/lib/php/extensions/no-debug-non-zts-20090626/suhosin.so" in Unknown on line 0PHP Warning: PHP Startup: Unable to load dynamic library ‘/usr/local/lsws/lsphp5/lib/php/extensions/no-debug-non-zts-20090626/xcache.so’ – Cannot open "/usr/local/lsws/lsphp5/lib/php/extensions/no-debug-non-zts-20090626/xcache.so" in Unknown on line 0PHP 5.3.0 with Suhosin-Patch (litespeed) (built: Sep 13 2009 22:29:50)
Copyright (c) 1997-2004 The PHP Group
Zend Engine v2.3.0, Copyright (c) 1998-2009 Zend Technologies

IMPORTANT :
This is mean you need to recompile XCACHE and SUHOSIN Packages.

Restart Litespeed Webserver

#/usr/local/lsws/bin/lswsctrl stop
#/usr/local/lsws/bin/lswsctrl start

Here is the PHPINFO result :

When you use chown to change ownership of a file or directory, it will work but with Symlink (Created by using lncommand), you can’t do that. When you do it, it will fail and you may not know that since there is no error message or anything to let you know. So, to change ownership for Symlink, you need to use option -h. Below is an example :

chown -h user:group symlink

Be careful when you use it with directory. Not to have trailing slash (/) at the end or it won’t work. So, if you have a Symlink directory name munin What you have to do is :

chown -h root:root /var/www/munin

not

chown -h root:root /var/www/munin/