Make a backup of the php.ini file by typing:

cp php.ini php.ini.bak

Edit the php.ini file.

Change the upload_max_filesize from the 2 MB default to something greater like 64 MB.

Change the post_max_size from the 2 MB default to something greater like 64 MB.

To add more allowable file types, navigate to the wp-includes directory of your WordPress site.  There, edit the functions.php file.

In the get_allowed_mime_types() function, add the desired file type using the existing file types as an example for the format.  A useful link for a list of MIME types: http://support.microsoft.com/kb/936496

yum -y install wget gcc gcc-c++ autoconf automake make
wget http://haproxy.1wt.eu/download/1.4/src/haproxy-1.4.20.tar.gz /download
tar -zxf haproxy-1.4.20.tar.gz
cd haproxy-1.4.20
make TARGET=linux26
cp haproxy /usr/sbin/haproxy
vi /etc/haproxy.cfg

Sample /etc/haproxy.cfg file:

global
      maxconn 4096
      pidfile /var/run/haproxy.pid
      daemon

defaults
      mode http
      retries 3
      option redispatch
      maxconn 2000
      contimeout 5000
      clitimeout 50000
      srvtimeout 50000

listen aprimo873lb 10.252.33.105:80
      mode http
      cookie APRIMO873LB insert
      balance roundrobin
      option httpclose
      option forwardfor
      stats enable
      stats auth myuser:mypass
      server aprimow1 10.252.33.173:80 cookie arpimo873lb_aprimow1 check
      server aprimow2 10.252.33.174:80 cookie aprimo873lb_aprimow2 check

Start the load balancer:

haproxy -f /etc/haproxy.conf

Add the above line to /etc/rc.local file to have haproxy start at bootup.

When I get around to it, I would like to set up an SSL load balancer using something similar to this:
http://blog.phpontrax.com/2010/02/how-to-make-an-open-source-load-balancer-stunnel-haproxy/

At the end of your /etc/rc.local file add in lines that will pause for a bit and then power on your next vm like so:

sleep 20
xe vm-start uuid=[uuid1]

sleep 20
xe vm-start uuid=[uuid2]

sleep 20
xe vm-start uuid=[uuid3]

etc…
The uuid is the unique identifier for the vm which can be found in XenCenter when you look at the VM’s general tab.

mount /dev/xvdd /mnt/
cd /mnt/Linux

For 32 bit:

rpm -Uhv xe*i386.rpm

For 64 bit:

rpm -Uhv xe*x86_64.rpm

Reboot the server.

yum -y install wget
yum -y install perl

1. Download it.

wget -c http://prdownloads.sourceforge.net/webadmin/webmin-1.580-1.noarch.rpm /download

2. Install it.

rpm -Uvh  webmin-1.580-1.noarch.rpm

DECLARE @name VARCHAR(50) -- database name
DECLARE @path VARCHAR(256) -- path for backup files
DECLARE @fileName VARCHAR(256) -- filename for backup
DECLARE @fileDate VARCHAR(20) -- used for file name 

SET @path = 'D:\SQLBackups\'  

SELECT @fileDate = CONVERT(VARCHAR(20),GETDATE(),112) 

DECLARE db_cursor CURSOR FOR
SELECT name
FROM master.dbo.sysdatabases
WHERE name NOT IN ('master','model','msdb','tempdb')  

OPEN db_cursor
FETCH NEXT FROM db_cursor INTO @name   

WHILE @@FETCH_STATUS = 0
BEGIN
       SET @fileName = @path + @name + '_' + @fileDate + '.BAK'
       BACKUP DATABASE @name TO DISK = @fileName  

       FETCH NEXT FROM db_cursor INTO @name
END   

CLOSE db_cursor
DEALLOCATE db_cursor 

Set this up in Task Scheduler to to automatically execute it at a scheduled time.  The command line to call the script is something like this:

sqlcmd -S localhost -E -i D:\SQL_Scripts\sp_BackupAllDatabases.sql

http://www.symantec.com/business/support/index?page=content&id=TECH86251&actp=search&viewlocale=en_US&searchid=1327899255372

Then run through the procedures to install and configure the remote agent:

http://www.symantec.com/business/support/index?page=content&id=TECH46461&actp=search&viewlocale=en_US&searchid=1327897044799

yum install samba

After the installation is complete, check for a file called mount.cifs.  It was not installed with my server build.

/etc/mount.cifs

If it is not there, install files to support for cifs.  After doing this install, the mount.cifs file magically appeared.

yum install cifs

Create a mount point where you plan to mount the Windows share.

mkdir /mnt/win

Modify the fstab file with information that will be used to connect when your CentOS server boots up.

vi /etc/fstab

The file may end up looking something like this.

#
# /etc/fstab
# Created by anaconda on Sun Jan 29 11:02:02 2012
#
# Accessible filesystems, by reference, are maintained under '/dev/disk'
# See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info
#
UUID=0db4ea35-aae2-4fa5-b3ab-734465f0d4f6 /                       ext4    defaults        1 1
UUID=40652af2-9ac8-47ce-b77b-f3f3ab16ff7b /boot                   ext4    defaults        1 2
UUID=4ab7e510-986b-4de7-bcbd-ed262822b06e swap                    swap    defaults        0 0
tmpfs                   /dev/shm                tmpfs   defaults        0 0
devpts                  /dev/pts                devpts  gid=5,mode=620  0 0
sysfs                   /sys                    sysfs   defaults        0 0
proc                    /proc                   proc    defaults        0 0
//server/Share          /mnt/win                cifs    user,uid=500,rw,suid,username=username,password=P@ssw0rd,workgroup=WinDomain 0 0

Now go ahead and reboot your CentOS server. With any luck, you’ll be able to see the contents of your Windows share under the mount point created earlier.

/mnt/win

"wSS2008!"

/etc/sysconfig/network-scripts

The file corresponding to eth0 is

ifcfg-eth0

Use a text editor to make it look something like this:

DEVICE="eth0"
NM_CONTROLLED="yes"
ONBOOT=yes
TYPE=Ethernet
BOOTPROTO=none
IPADDR=192.168.1.100
PREFIX=24
GATEWAY=192.168.1.1
DNS1=192.168.1.2
DNS2=4.2.2.2
DOMAIN=domain.com
DEFROUTE=yes
IPV4_FAILURE_FATAL=yes
IPV6INIT=no
NAME="System eth0"
UUID=5fb06bd0-0bb1-7ffa-44f1-d6eda65f2e03
HWADDR=00:01:01:12:34:56

After you save your changes, you’ll need to restart your network service with this command:

service network restart

You should be able to ping the address you just configured, but you might not be able to ping it from another client or even ping out.  This has to do with your firewall settings, but that’s something that will be covered in another post.