I am outlining the steps for my server, ie. CentOs 5.2 with Apache 2.2

• wget http://dl.atrpms.net/all/mod_limitipconn-0.23-4.el5.x86_64.rpm
• rpm -i mod_limitipconn-0.23-4.el5.x86_64.rpm
• vi /etc/http/modules/ipconn.conf
  

  Add following to the content of ipconn.conf
  # LimitIPConn module limits the number of connection to apache
  # per IP address. This helps in limiting the simultaneous downloads and will help
  # prevent slow users from blocking your servers.
  #
  <IfModule prefork.c>
  LoadModule limitipconn_module modules/mod_limitipconn.so
  </IfModule>

• Make sure ‘ExtendedStatus‘ is ON in /etc/httpd/conf/httpd.conf
• You will have to configure the module for each of your virtual host that you need to implement the limitip for.
  

  <IfModule mod_limitipconn.c>
  <Location /forums>
  MaxConnPerIP 3
  # exempting images from the connection limit is often a good
  # idea if your web page has lots of inline images, since these
  # pages often generate a flurry of concurrent image requests
  NoIPLimit image/*
  </Location>
  <Location /video>
  MaxConnPerIP 1
  # In this case, all MIME types other than audio/mpeg and video*
  # are exempt from the limit check
  OnlyIPLimit audio/mpeg video
  </Location>
  </IfModule>

• Save the config file and test the new configuration “/etc/init.d/httpd configtest”. If you get “Syntax OK”, then all you need to do is restart the server and you are good to go.

This is a brief guide on how I got mod_limitipconn working on my server. If you have any questions, please feel free to post in comment and I will try to answer your questions.

It’s very easy to sync up the time in Linux/Unix. Issue the following command as ‘root’ to update the time.

ntpdate pool.ntp.org

To automate this time update, you can set up a cron job to run once every week.

Then I found that in the lower left corner, there’s a box with “Host Summary”. You have to add your nameservers entry in that box first. So click on “Add” besides “Host Summary” and it will present you another dialog where you can enter your subdomain and the ip address to point to your server. Once you have added your nameservers in Host Summary, then you can click on “Manage” besides “NameServers” and add your nameservers ns1.xxxx.com and ns2.xxxx.com there and Godaddy will happily accept it!!

Hope this saves you your time and help you avoid pulling your hair!!!

#!/bin/bash
unset PATH

# USER VARIABLES
BACKUPDIR=/disk3                            # Folder on the backup server where the backups shall be located
#KEY=/root/.ssh/id_rsa                        # SSH key
#MYSQL_BACKUPSCRIPT=/root/my_backup.sh        # Path to the remote mysql backup script
#PRODUCTION_USER=root@production.server.com    # The user and the address of the production server
EXCLUDES=/disk1/backup_exclude                # File containing the excluded directories
DAYS=60                                        # The number of days after which old backups will be deleted

# PATH VARIABLES
SH=/bin/sh                                    # Location of the bash bin in the production server!!!!

CP=/bin/cp;                                    # Location of the cp bin
FIND=/usr/bin/find;                            # Location of the find bin
ECHO=/bin/echo;                                # Location of the echo bin
MK=/bin/mkdir;                                # Location of the mk bin
SSH=/usr/bin/ssh;                            # Location of the ssh bin
DATE=/bin/date;                                # Location of the date bin
RM=/bin/rm;                                    # Location of the rm bin
GREP=/bin/grep;                                # Location of the grep bin
MYSQL=/usr/bin/mysql;                        # Location of the mysql bin
MYSQLDUMP=/usr/bin/mysqldump;                # Location of the mysql_dump bin
RSYNC=/usr/bin/rsync;                        # Location of the rsync bin
TOUCH=/bin/touch;                            # Location of the touch bin

##                                                      ##
##      –       DO NOT EDIT BELOW THIS HERE     –     ##
##                                                      ##

# CREATING NECESSARY FOLDERS
$MK $BACKUPDIR
CURRENT=$BACKUPDIR/current
OLD=$BACKUPDIR/old
$MK $CURRENT
$MK $OLD
# CREATING CURRENT DATE / TIME
NOW=`$DATE ‘+%Y-%m’-%d_%H:%M`
NOW=$OLD/$NOW
$MK $NOW

# CREATE REMOTE MYSQL BACKUP BY RUNNING THE REMOTE BACKUP SCRIPT
# $SSH -i $KEY $PRODUCTION_USER “$SH $MYSQL_BACKUPSCRIPT”

# RUN RSYNC INTO CURRENT
#$RSYNC                                                            \
#    -apvz –delete –delete-excluded                        \
#     –exclude-from=”$EXCLUDES”                                \
#      -e “$SSH -i $KEY”                                        \
#       $PRODUCTION_USER:/                                        \
#        $CURRENT ;

// No Compression
$RSYNC                                                            \
-apv –delete –delete-excluded                        \
–exclude-from=”$EXCLUDES”                                \
/                                \
$CURRENT ;

# UPDATE THE MTIME TO REFELCT THE SNAPSHOT TIME
$TOUCH $BACKUPDIR/current

# MAKE HARDLINK COPY
$CP -al $CURRENT/* $NOW

# REMOVE OLD BACKUPS
for FILE in “$( $FIND $OLD -maxdepth 1 -type d -mtime +$DAYS )”
do
#    $RM -Rf $FILE
$ECHO $FILE
done
exit 0

Save the following to /disk3/backup_exclude. Essentially, these are the files/folders you do not wish to backup using rsync.

/disk3/
/bin/
/boot/
/dev/
/lib/
/lost+found/
/mnt/
/opt/
/proc/
/sbin/
/sys/
/tmp/
/usr/
/var/log/
/var/spool/
/var/lib/php4/
/var/lib/mysql/

My System setup is:

• Ubuntu 8.10
• Eclipse Ganymede (3.4) with CDT

Follow the steps to get black background with white foreground for source code editing part of eclipse.

1. Select Window -> Preferences -> C/C++ (language editor you need to change for) -> Editor. In the Appearance color options change the following
   • Matching brackets highlight (Color #FFA500)
   • Inactive code highlight (Color #302E2E)
   • Completion Proposal background (Color #000000)
   • Completion Proposal foreground (Color #FFFFFF)
   • Parameter Hint Background (Color #000000)
   • Parameter Hint Foreground (Color #FFFFFF)
   • Source Hover Background (Color #F5F5B5)
2. Select Window -> Preferences -> C/C++ (language editor you need to change for) -> Editor -> Syntax Coloring
   • In the Code, change all the ones with black color to white and vice versa and leave the rest as they are.

This will give you the colors you want. I know its tedious but that’s the only way to do it at present.

diff -rup /home/ketan/unmodified_source.c /home/ketan/modified_source.c > patch.source.c

Now to apply patch to the original unmodified source. Use the following command from the appropriate location (/home/ketan) in our example.

patch -p0 < patch.source.c

Check it out today, ‘readelf -a <binary_executable>‘

gpasswd -a ketan  admin

Such a simple and each to use command!!!

To create the repository for first time, issue the following command

svnadmin create –fs-type fsfs /var/www/subversion/kpsolution

Then to import your code for first time, go to your base directory of the source tree and then issue the following command

svn import -m “Initial Import” . file:///var/www/subversion/kpsolution/

Now, you have imported your source code into the repository and then use the SVN GUI to checkin/checkout the changes.

For more detailed instruction on setting up the svn, see “http://www.rockfloat.com/howto/gentoo-subversion.html”

/etc/init.d/mysqld stop

Then I looked at the error-log file for mysql in /var/log/mysql-error.log and found that the disk didn’t had any empty space left and correctly enough, when I did

df -h

I saw that the /var mounted partition didn’t had any diskspace remaining. To find the exact culprit I looked around in the /var directory and found that the ‘mysqld.log’ file was 9GB large. I was puzzled as to how come this log grew so big. Thoughts came that the server would have been compromised but the actual culprit was the my.cnf file for the mysql. During the setup of the server, by mistake I had put a statement

[mysqld]

log=/var/log/mysqld.log

This configuration was causing to save all the queries that were performed on the mysql server since it booted. Naturally on a high traffic site, you will see this file grow huge quickly. I learned the lesson hard way, but always RTFM when you are configuring something on the production server. So for solution, all I had to was remove the mysqld.log file and comment out the above “log” configuration in the my.cnf.

I thought to post this out there to help other people in case they have the same issue.