Also please read the ASSP documentation

Preliminary Note

In this tutorial I use a base 32 bit server install with the hostname server1.example.co.za with the IP address 10.0.0.10. These settings might differ for you, so you have to replace them where appropriate.

Adjust any package names if installing the EL4 or 64 bit packages. If any dependencies are unsatisfied, install the required packages and retry

If you have already installed the RPM Forge repository do so by running the following command

# rpm -Uhv http://apt.sw.be/redhat/el5/en/i386/rpmforge/RPMS/rpmforge-release-0.3.6-1.el5.rf.i386.rpm

Now lets install the Perl components needed to run ASSP (Anti-Spam SMTP Proxy) on CentOS 5.4. Firstly we upgrade Perl and then install the Perl modules.

# yum upgrade perl
# yum install perl-IO-Compress perl-Net-DNS perl-Email-Valid perl-File-ReadBackwards perl-Mail-SPF-Query perl-Mail-SRS perl-LDAP perl-MIME-tools perl-File-Scan-ClamAV

If and in order to run ClamAV anti-virus along with ASSP (Anti-Spam SMTP Proxy) install the ClamAV RPM

# yum install clamd
# chkconfig clamd on
# service clamd start

Next we'll download and install ASSP (Anti-Spam SMTP Proxy)

Firstly check and grab the link for the latest version of ASSP on thier website, the version used in this post is ASSP Version: 1.6.5.5(1.0.02). Copy the direct download link for the latest version and download it.

Lets get ASSP.

# wget http://downloads.sourceforge.net/project/assp/ASSP%20Installation/ASSP%201.6.5.5/ASSP_1.6.5.5-Install.zip?use_mirror=ufpr

Make some preparations. Create the following directories that ASSP (Anti-Spam SMTP Proxy) will use to maintain the SPAM

# mkdir -p /usr/share/assp/spam
# mkdir /usr/share/assp/notspam
# mkdir /usr/share/assp/errors
# mkdir /usr/share/assp/errors/spam
# mkdir /usr/share/assp/errors/notspam

Now unpack ASSP.

# unzip ASSP_1.6.5.5-Install.zip
# cd ASSP_1.6.5.5-Install

And put ASSP in place.

# mv -f ASSP/* /usr/share/assp

Create following startup scripts.

# vi /etc/init.d/assp

#!/bin/bash
#
# chkconfig: 2345 80 05
# Description: ASSP init.d script
# Hacked by : How2CentOS - http://www.how2centos.com

# Get function from functions library
. /etc/init.d/functions

# Start the service ASSP
start() {
        echo -n "Starting ASSP server: "
        cd /usr/share/assp
        perl assp.pl 2>&1 > /dev/null &
        ### Create the lock file ###
        touch /var/lock/subsys/ASSP
        success $"ASSP server startup"
        echo
}

# Restart the service ASSP
stop() {
        echo -n "Stopping ASSP server: "
        kill -9 `ps ax | grep "perl assp.pl" | grep -v grep | awk '{ print $1 }'`
        ### Now, delete the lock file ###
        rm -f /var/lock/subsys/ASSP
        success $"ASSP server shutdown"
        echo
}

### main logic ###
case "$1" in
  start)
        start
        ;;
  stop)
        stop
        ;;
  status)
        status ASSP
        ;;
  restart|reload|condrestart)
        stop
        start
        ;;
  *)
        echo $"Usage: $0 {start|stop|restart|reload|status}"
        exit 1
esac

exit 0

Lets start ASSP for the first time.

# cd /usr/share/assp
# perl assp.pl

You should be able to connect to ASSP web interface at this point. http://server1.example.co.za:55555. Specify anything for "username", default "password" is nospam4me

At this point you shall see that ASSP is unable to bind to port 25. We need to stop and disable CentOS default mailer Sendmail.

# service sendmail stop
# chkconfig sendmail off

or

# yum remove sendmail

Now let's shutdown ASSP with "Ctrl-C". Now add the init script to chkconfig, set the run levels and start ASSP.

# chmod 755 /etc/init.d/assp
# chkconfig --add assp
# chkconfig assp on
# service assp start

Now lets do some minimal ASSP Configuration, point you browser to http://server1.example.co.za:55555

Network Setup

* SMTP Listen Port 25
* SMTP Destination 25

SMTP Session Limits
Testmode

* All Testmode ON - Running in this mode for two weeks to build the spamdb and whitelist

SPAM Control

* Prepend Spam Subject {ASSP-SPAM}

Copy Spam & Ham
Spam Lover/Hater
No Processing
Redlisting/Whitelisting
Relaying
Recipients
Validate Helo
Validate Sender
IP Blocking
Penalty Box
Delaying
SPF/SRS
DNSSBL
URIBL
Attachment Blocking
ClamAV

* Port or file socket for ClamAV (AvClamdPort) - /var/run/clamav/clamd.sock

Regex Filters / Spambomb
Bayesian Options
Backscatter Detection
Email Interface
File Paths
Collecting
Logging
LDAP Setup
DNS Setup
Server Setup

After a week rebuild the bayes database. Check the directories /usr/share/assp/spam and nospam for wrong entries, if good mail ends up in the spam directory please move it to the nospam directory and vice versa. After that do:

# cd /usr/share/assp
# perl rebuildspamdb.pl

Finally let's add the bayes database rebuild to crontab.

# crontab -e

#       minute (0-59),
#       |       hour (0-23),
#       |       |       day of the month (1-31),
#       |       |       |       month of the year (1-12),
#       |       |       |       |       day of the week (0-6 with 0=Sunday).
#       |       |       |       |       |       commands
# -----------[ cron jobs  ]------------ #

# Weekly rebuild of the bayes database
		* 	  * 	  * 	  * 	  0 	   cd /usr/share/assp && perl rebuildspamdb.pl

No related posts.

Below is the output from the svnsync showed this:

# /usr/bin/svnsync --non-interactive synchronize svn://{destination repository}/opt/svn/{repo}

Failed to get lock on destination repos, currently held by 'svn.how2centos.com:fbc2c0c8-957f-0410-8a06-87f31314868b'
Failed to get lock on destination repos, currently held by 'svn.how2centos.com:fbc2c0c8-957f-0410-8a06-87f31314868b'
Failed to get lock on destination repos, currently held by 'svn.how2centos.com:fbc2c0c8-957f-0410-8a06-87f31314868b'
Failed to get lock on destination repos, currently held by 'svn.how2centos.com:fbc2c0c8-957f-0410-8a06-87f31314868b'
Failed to get lock on destination repos, currently held by 'svn.how2centos.com:fbc2c0c8-957f-0410-8a06-87f31314868b'
Failed to get lock on destination repos, currently held by 'svn.how2centos.com:fbc2c0c8-957f-0410-8a06-87f31314868b'
Failed to get lock on destination repos, currently held by 'svn.how2centos.com:fbc2c0c8-957f-0410-8a06-87f31314868b'
Failed to get lock on destination repos, currently held by 'svn.how2centos.com:fbc2c0c8-957f-0410-8a06-87f31314868b'
Failed to get lock on destination repos, currently held by 'svn.how2centos.com:fbc2c0c8-957f-0410-8a06-87f31314868b'
Failed to get lock on destination repos, currently held by 'svn.how2centos.com:fbc2c0c8-957f-0410-8a06-87f31314868b'
svnsync: Couldn't get lock on destination repos after 10 attempts

To remove the lock you'll need to do the following:

# svn propdel svn:sync-lock --revprop -r 0 svn://{destination repository}/opt/svn/{repo}
# /usr/bin/svnsync --non-interactive synchronize svn://{destination repository}/opt/svn/{repo}

Committed revision 1694.
Copied properties for revision 1694.
Committed revision 1695.
Copied properties for revision 1695.

Related posts:

1. #SVN #Apache #LDAP configuration

You need to document these as well as any other additional services or features (i.e. DHCP, DNS or VPN). This will assist you while you recreate the policies behind the firewall rules.

You can download a sample Firewall Planning Guide here:

Firewall Planning Guide (66)

Review policy changes
Before you begin review your Planning guides and decide if they're 1) Still valid? or 2) Is this what the customer needs?

The replacement of a key firewall is the perfect time to consider whether the current policy is the current best practice and/or whether it still fits the security needs of the company.

Determine any rule changes
Once you’re agreed on policy, check the existing firewall rules and functions to see what is in conformance, what is superfluous, and what needs to be added.

Test the new configuration on the firewall
This is an important step. Change your gateway to the new firewall which is running concurrently with the old and test. Firstly, this will let you determine whether or not the new rules are complete and working. Secondly, it won't interrupt day to day operations.

Move to the new firewall
If all is well migrate to the new firewall either by switching IP's or changing the default gateway in DHCP. Once the firewall is in place, acceptance testing will of course need to be carried out.

In case of emergency, the fact that you have the old firewall and new firewall set up allows you to quickly roll back to the old firewall and pull the new one out of service for checking and reconfiguration. Having this option available should reduce network downtime if there's a show stopper.

Adding new services
Wait until the new firewall is stable before adding new functions as this simplifies testing. Finally complete the migration by adding any new services that were requested, and since the configuration is known to be good and stable before adding the new services, any introduced instability should be easy to isolate and fix.

No related posts.

This How To will show you a simple yet effective way of setting up your local Fedora 12 YUM repository and client.

TIP: Distribute your Fedora YUM configuration via your Puppet Master

Preliminary Note:

I am using two Fedora 12 installations in this tutorial with server1.example.co.za configured with Apache httpd

* server1.example.co.za (IP 10.0.0.100): Fedora 12 YUM Repository and httpd server
* server2.example.co.za (IP 10.0.0.102): Fedora 12 YUM client

Configure Fedora YUM repo and httpd server as follows:

Create the following Directories:

# mkdir -p /var/www/html/fedora/12/os/i386
# mkdir -p /var/www/html/fedora/12/os/x86_64

Create a bash script that will rsync your local YUM Repository server with your local YUM mirror (Make sure the mirror supports rsync).

Fedora Mirror list - http://mirrors.fedoraproject.org/publiclist

# vi fedora-repo-update.sh

#!/bin/sh

rsync="rsync -avrt --bwlimit=256"

mirror=mirrors.kernel.org::mirrors/fedora

verlist="12"
archlist="i386 x86_64"
baselist="os"
local=/var/www/html/fedora/

for ver in $verlist
do
 for arch in $archlist
 do
  for base in $baselist
  do
    remote=$mirror/releases/$ver/Fedora/$arch/$base/
    $rsync $remote $local/$ver/$base/$arch/
  done
 done
done

# chmod 755 fedora-repo-update.sh

Add the bash script to your crontab to update your local repository every night (01H00 in this case)

# crontab -e

#       minute (0-59),
#       |       hour (0-23),
#       |       |       day of the month (1-31),
#       |       |       |       month of the year (1-12),
#       |       |       |       |       day of the week (0-6 with 0=Sunday).
#       |       |       |       |       |       commands
# -----------[ cron jobs  ]------------ #

# Update Local YUM repo update from fedora.mirror.facebook.net
	 0 	  1 	  * 	  * 	  * 	   /path/to/fedora-repo-update.sh

Configure Fedora YUM client servers as follows:

Rename all existing yum repositories from *.repo to *.old

# vi /etc/yum.repos.d/localFedora.repo

[base]
name=Fedora $releasever - $basearch
failovermethod=priority
baseurl=http://server1.example.co.za/fedora/$releasever/$basearch/os/
enabled=1
gpgcheck=0

Test your setup by running a yum update on your client machine.

# yum update

Loading "fastestmirror" plugin
Loading mirror speeds from cached hostfile
* update: server1.example.co.za
* base: server1.example.co.za

Related posts:

1. Creating a Local #Fedora 11 #Yum Repository
2. Creating A Local #Yum Repository on #CentOS 5.x
3. Adding #CentOS 5.3 to Local #YUM Repository

Fedora 12 Overview

As always, Fedora continues to develop (http://www.fedoraproject.org/wiki/Red_Hat_contributions) and integrate the latest free and open source software (http://www.fedoraproject.org/wiki/Features). The following sections provide a brief overview of major changes from the previous release of Fedora.

For more details about other features that are included in Fedora 12 refer to their individual wiki pages that detail feature goals and progress:
http://www.fedoraproject.org/wiki/Releases/12/FeatureList

Throughout the release cycle, there are interviews with the developers behind key features giving out the inside story:
http://www.fedoraproject.org/wiki/Interviews

The following are major features for Fedora 12:
* Improved WebCam support
* Better Video Codec
* Audio Improvements
* Better Power Management

Some other features in this release include:
* Automatic bug reporting tool
* Bluetooth on demand
* Many, many virtualization enhancements
* Still more security improvements

Features for Fedora 12 tracked on the feature list page:
http://www.fedoraproject.org/wiki/Releases/12/FeatureList

A discussion putting these features in context may be found at:
http://www.fedoraproject.org/wiki/Fedora_12_Talking_Points

Original Document: http://docs.fedoraproject.org/release-notes/f12/en-US/html/

Related posts:

1. #Fedora 11: #Leonidas – Released
2. Creating a Local #Fedora 12 #Yum Repository
3. Creating a Local #Fedora 11 #Yum Repository

Reason: Within the Asterisk Kernel, it is coded to play the [default] Message on Hold (MOH) class, which is the same for all calls made internally to another extension. You can create many MOH classes, but only the [default] is used for external calls. It is also a bug in the way LibPRI processes ISDN on-hold frames, and won’t be fixed in current Asterisk 1.4, but will be an option to turn this off in DAHDI Asterisk 1.6 (so I have read). We have tried and tested 1.6, and was introduced to a whole new range of problems (other advice - stick to 1.4!). Asterisk also has issues interpreting certain DTMF tones, so does not know when to unhold a call, because never receives or interprets the unhold tone sent by remote PBX system. On the 'Outbound Routes' option in FreePBX, you can set the MOH to none, but does not work, still uses default.

Relates to:

AsteriskNOW
Trixbox
Elastix - My best choice of a complete Asterisk PBX Solution!
Other Asterisk installed by source, possibly on Ubuntu

All the above are available for ISO download, and based on CentOS 5 Core.

Solutions

a) Hire a very expensive Asterisk Guru to recode your current Asterisk Kernel to suit you (other issues will arise, and you will have to folk out a lot more money)...

OR

b) Simply do it yourself with the tools provided in three easy steps! After many late nights Googling and trying to figure out the Kernel / Code myself, I came up with a very simple, right in front of you, simple solution. The only downfall here, is that internally dialed extensions (you to a work mate) will not play music on hold, the person on hold will only hear silence, which is worth it!

Create a new Music on Hold class, and configure the music.

Firstly browser to your FreePBX GUI, navigate to 'Music on Hold', select 'Add Music Category', and give it a name. For now I will name it CompanyA.

In your Linux console, this will create a folder in /var/lib/asterisk/mohmp3/CompanyA/

# ll /var/lib/asterisk/mohmp3/

Copy your music from /var/lib/asterisk/mohmp3/ to this new directory:

# cp /var/lib/asterisk/mohmp3/*.mp3 (or WAV) /var/lib/asterisk/mohmp3/CompanyA

Change ALL your Inbound Lines and Queues

Next Change ALL your Inbound Lines and Queues within FreePBX GUI to use this new MOH class 'CompanyA'. You dont have to do this for inbound Fax lines if you are making use of Fax to Email, like Hylafax. I left mine as Default.

You can script this, but its a much longer process to create a script, rather than simply doing it via the GUI. If you backup your asterisk folder, or rsync it, then change a field or two in FreePBX, then run rsync again or diff on the files, it changes more than one config file, and just becomes confusing. Get your IT desktop guy to do the manual work, otherwise please post the script!

Edit config file and restart Asterisk

Finally all you need to do is edit a config file, reload Asterisk, and you're done!

# vim /etc/asterisk/musiconhold_additional.conf

Comment out the [default] MOH class to point to /dev/null (this deactivates the MOH feature completely for this class). Comment out and add for easy roll-back, always think ahead!

[CompanyA]
mode=files
directory=/var/lib/asterisk/mohmp3/CompanyA/
random=yes

[default]
mode=files
directory=/dev/null

;[default]
;mode=files
;directory=/var/lib/asterisk/mohmp3/

FINALLY - in FreePBX, 'Reload Asterisk'... and you're done!

Result: From here, when you make an outbound call, and you are put on hold, you will hear the dialed party's Music on Hold (or whatever they have) instead of yours. This reassures you that the call has not dropped, and you are still on hold. There is no DTMF tones or frames that your Asterisk box has to interpret, taking the fault away from your side. Your CEO will be happy that now he can actually wait on hold for a board member and not be cut off, and wondering why they called person has not come back to him.

No related posts.

What is Remus?

Remus provides transparent, comprehensive high availability to ordinary virtual machines running on the Xen virtual machine monitor. It does this by maintaining a completely up-to-date copy of a running VM on a backup server, which automatically activates if the primary server fails. Key features:

* The backup VM is an exact copy of the primary VM. When failure happens, it continues running on the backup host as if failure had never occurred.
* The backup is completely up-to-date. Even active TCP sessions are maintained without interruption.
* Protection is transparent. Existing guests can be protected without modifying them in any way.

For a full description and evaluation, see their NSDI paper.

Visit the project: http://dsg.cs.ubc.ca/remus/

Related posts:

1. How to install #XEN 3.4.1 on #CentOS 5.4
2. Installing #XEN on #CentOS 5.x

BitNami Native Installers automate the setup of a BitNami Stack on Windows, Linux or Mac OS X. Each installer includes all of the software necessary to run out of the box (the Stack). The process is simple; just download, click next-next-next and you are done! BitNami Stacks are completely self contained and will not interfere with other software on your system.

http://bitnami.org/

What is Jasper for MySQL?

JasperServer Professional is a high-performance standalone and embeddable report server that provides non-technical business users with:

* Drag and drop ad hoc report building
* Drag and drop dashboarding with live-refresh, and mash-ups with external content
* A rich business metadata layer for easy ad hoc query
* Integrated and in-memory data analysis
* Built-in charting and integration with third-party visualization tools
* Self-service parameterized web reporting
* Report scheduling, distribution and historical versioning
* A secure report and metadata repository
* Access to any data source including relational, XML, Hibernate, EJB, POJO, and custom
* Row and column level data security

http://www.jaspersoft.com/jasperserver

Preliminary Note:

I am using a CentOS 5.4 x86_64 base installation in this tutorial

* server1.example.co.za (IP 10.0.0.100): CentOS 5.4 x86_64 Base installation

Download and Install BitNami JasperSever Stack

# wget http://bitnami.org/files/stacks/jasperserver/bitnami-jasperserver-3.5.0-0-linux-installer.bin
# chmod 755 ./bitnami-jasperserver-3.5.0-0-linux-installer.bin
# ./bitnami-jasperserver-3.5.0-0-linux-installer.bin

----------------------------------------------------------------------------
Welcome to the BitNami JasperServer Stack Setup Wizard.

----------------------------------------------------------------------------
Installation folder

Please, choose a folder to install BitNami JasperServer Stack

Select a folder [/opt/jasperserver-3.5.0-0]:

----------------------------------------------------------------------------
MySQL Information

Please enter your MySQL database information:

MySQL Server port [3306]:

----------------------------------------------------------------------------
MySQL Credentials

Please enter your database root user password

MySQL Server root password :
Re-enter password :
----------------------------------------------------------------------------
Setup is now ready to begin installing BitNami JasperServer Stack on your computer.

Do you want to continue? [Y/n]:

In this installation I went ahead and chose all the defaults

Note: if you get this error:

-bash: ./bitnami-jasperserver-3.5.0-0-linux-installer.bin: /lib/ld-linux.so.2: bad ELF interpreter: No such file or directory

make sure the i386 version of ibstdc++ is installed:

# rpm -qa | grep ibstdc++
# yum install libstdc++

Starting and Stopping the JasperServer

# ./catalina.sh start
# ./catalina.sh stop

Once you have started the JasperServer point your browser to the following URL to access the JasperServer GUI

http://server1.example.co.za:8080/jasperserver/login.html

Now your MySQL reporting can begin.

Related posts:

1. Installing #Cherokee with #PHP 5.2.10 and MySQL Support On #CentOS 5.3

Installing the psacct package

Use yum command if you are using CentOS 5.4 / Fedora 11 / RHEL 5.4:

# yum install psacct

Start psacct service

By default service is not started on RHEL 5.4 / Fedora 11 / CentOS 5.4 you need to start psacct service manually. Type the following two commands to create /var/account/pacct file and start services:

# chkconfig psacct on
# service psacct start

Display statistics about users' connect time

ac prints out a report of connect time (in hours) based on the logins/logouts in the current wtmp file. A total is also printed out.

# ac

total       95.08

Print totals for each day rather than just one big total at the end.

# ac -d

Jul  3  total     1.17
Jul  4  total     2.10
Jul  5  total     8.23
Jul  6  total     2.10
Jul  7  total     0.30

Print time totals for each user in addition to the usual everything-lumped-into-one value.

# ac -p

bob       8.06
goff      0.60
maley     7.37
root      0.12
total    16.15

Find out information about previously executed user commands

lastcomm prints out information about previously executed commands. If no arguments are specified, lastcomm will print info about all of the commands in acct (the record file).

# lastcomm root

userhelper        S   X	root  pts/0      0.00 secs Mon Nov 13 23:58
userhelper        S     root  pts/0      0.00 secs Mon Nov 13 23:45
rpmq                    root  pts/0      0.01 secs Mon Nov 13 23:45
rpmq                    root  pts/0      0.00 secs Mon Nov 13 23:45
rpmq                    root  pts/0      0.01 secs Mon Nov 13 23:45
gcc                     root  pts/0      0.00 secs Mon Nov 13 23:45
which                   root  pts/0      0.00 secs Mon Nov 13 23:44
bash               F    root  pts/0      0.00 secs Mon Nov 13 23:44
ls                      root  pts/0      0.00 secs Mon Nov 13 23:43
rm                      root  pts/0      0.00 secs Mon Nov 13 23:43
vi                      root  pts/0      0.00 secs Mon Nov 13 23:43
ping              S     root  pts/0      0.00 secs Mon Nov 13 23:42
ping              S     root  pts/0      0.00 secs Mon Nov 13 23:42
ping              S     root  pts/0      0.00 secs Mon Nov 13 23:42
cat                     root  pts/0      0.00 secs Mon Nov 13 23:42
netstat                 root  pts/0      0.07 secs Mon Nov 13 23:42
su                S     root  pts/0      0.00 secs Mon Nov 13 23:38

For each entry the following information is printed:
          + command name of the process
          + flags, as recorded by the system accounting routines:
               S -- command executed by super-user
               F -- command executed after a fork but without a following exec
               C -- command run in PDP-11 compatibility mode (VAX only)
               D -- command terminated with the generation of a core file
               X -- command was terminated with the signal SIGTERM
          + the name of the user who ran the process
          + time the process exited

Search the accounting logs by command name:

# lastcomm rm
# lastcomm passwd

rm                      root     pts/0      0.00 secs Tue Nov  3 07:34
rm                      root     pts/0      0.00 secs Tue Nov  3 07:34
rm                      root     pts/0      0.00 secs Tue Nov  3 07:33
rm                      root     pts/0      0.00 secs Tue Nov  3 07:33
rm                      root     pts/0      0.00 secs Tue Nov  3 07:14
rm                      root     pts/0      0.00 secs Tue Nov  3 07:14

Search the accounting logs by terminal name pts/0

# lastcomm pts/0

Summarizes accounting information

sa summarizes information about previously executed commands as recorded in the acct file. In addition, it condenses this data into a summary file named savacct which contains the number of times the command was called and the system resources used. The information can also be summarized on a per-user basis; sa will save this information into a file named usracct.

# sa

   26100      26.62re       0.00cp      931k   who
   75980     161.69re       0.00cp      979k   grep
   23756       3.93re       0.00cp      938k   cut
    1283     815.91re       0.00cp     1327k   crond*
       6       4.89re       0.00cp     2102k   sshd*
       4       0.01re       0.00cp     1274k   grotty
       2      33.19re       0.00cp     1624k   scp
      25       0.04re       0.00cp      447k   mail
      15       0.05re       0.00cp      472k   ntpdate

Take example of first line:

26100      26.62re       0.00cp      931k   who

Where,

* 26.62re "real time" in wall clock minutes
* 0.00cp sum of system and user time in cpu minutes
* 931k cpu-time averaged core usage, in 1k units
* who command name

For each command in the accounting file, print the userid and command name.

# sa -u

root       0.00 cpu      595k mem accton
root       0.00 cpu    12488k mem initlog
root       0.00 cpu    12488k mem initlog
root       0.00 cpu    12482k mem touch
root       0.00 cpu    13226k mem psacct
root       0.00 cpu      595k mem consoletype
root       0.00 cpu    13192k mem psacct           *
root       0.00 cpu    13226k mem psacct
root       0.00 cpu    12492k mem chkconfig

Print the number of processes and number of CPU minutes on a per-user basis.

# sa -m

                                   973902  107317.71re    1337.92cp     2101k
root                               781510   95856.57re     559.01cp     1795k
apache                                334    9007.96re     513.05cp    25916k
nagios                             192035    2447.62re     265.85cp     3303k
smmsp                                  17       0.67re       0.00cp     2033k
sshd                                    6       4.89re       0.00cp     2102k

No related posts.

The Xen hypervisor, the powerful open source industry standard for virtualization, offers a powerful, efficient, and secure feature set for virtualization of x86, x86_64, IA64, ARM, and other CPU architectures. It supports a wide range of guest operating systems including Windows, Linux, Solaris, and various versions of the BSD operating systems.

Preliminary Note:

I’m using a CentOS 5.4 x86_64 base installation in this tutorial

* server1.example.co.za (IP 10.0.0.100): CentOS 5.4 x86_64 Base installation

Install the Gitco repository

Browse to http://www.gitco.de/repo/ and grab the latest repo for your arch. (in this case x86_64)

# cd /etc/yum.repos.d/
# wget http://www.gitco.de/repo/GITCO-XEN3.4.1_x86_64.repo

Remove previous installations of XEN before re-installing XEN 3.4.1

# yum groupremove Virtualization
# yum groupinstall Virtualization

Edit grub.conf to reflect the correct default Kernel

# vi /etc/grub.conf

# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE:  You have a /boot partition.  This means that
#          all kernel and initrd paths are relative to /boot/, eg.
#          root (hd0,0)
#          kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00
#          initrd /initrd-version.img
#boot=/dev/sda
default=0
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title CentOS (2.6.18-128.7.1.el5xen)
        root (hd0,0)
        kernel /xen.gz-3.4.1
        module /vmlinuz-2.6.18-128.7.1.el5xen ro root=/dev/VolGroup00/LogVol00
        module /initrd-2.6.18-128.7.1.el5xen.img
title CentOS (2.6.18-128.1.16.el5xen)
        root (hd0,0)
        kernel /xen.gz-3.4.1
        module /vmlinuz-2.6.18-128.1.16.el5xen ro root=/dev/VolGroup00/LogVol00
        module /initrd-2.6.18-128.1.16.el5xen.img
title CentOS (2.6.18-128.el5xen)
        root (hd0,0)
        kernel /xen.gz-3.4.1
        module /vmlinuz-2.6.18-128.el5xen ro root=/dev/VolGroup00/LogVol00
        module /initrd-2.6.18-128.el5xen.img
title CentOS (2.6.18-164.el5xen)
        root (hd0,0)
        kernel /xen.gz-3.4.1
        module /vmlinuz-2.6.18-164.el5xen ro root=/dev/VolGroup00/LogVol00
        module /initrd-2.6.18-164.el5xen.img

Reboot the machine for new XEN kernel to take effect

# reboot

After the reboot check the Kernel to reflect the change

# uname -r
2.6.18-128.7.1.el5xen

Related posts:

1. Installing #XEN on #CentOS 5.x
2. #Remus applied to the official #Xen repository