1. Login to your container/VPS via ssh as the root user. 2. Determine which version of CentOS you are running.
cat /etc/redhat-release
CentOS release 6.2 (Final)
or:
CentOS release 5.7 (Final)
or:
CentOS release 5.6 (Final)
or:
CentOS release 5.5 (Final)
3. Paste the commands for your CentOS version to your command line. CentOS 6.2:
rpm
-Uvh --nodeps http://mirror.ihug.co.nz/centos/6/os/$(uname
-i)/Packages/yum-metadata-parser-1.1.2-16.el6.$(uname
-i).rpm http://mirror.ihug.co.nz/centos/6/os/$(uname
-i)/Packages/yum-plugin-fastestmirror-1.1.30-10.el6.noarch.rpm
rpm -Uvh http://mirror.ihug.co.nz/centos/6/os/$(uname -i)/Packages/gpgme-1.1.8-3.el6.$(uname -i).rpm http://mirror.ihug.co.nz/centos/6/os/$(uname -i)/Packages/pygpgme-0.1-18.20090824bzr68.el6.$(uname -i).rpm http://mirror.ihug.co.nz/centos/6/os/$(uname -i)/Packages/python-iniparse-0.3.1-2.1.el6.noarch.rpm http://mirror.ihug.co.nz/centos/6/os/$(uname -i)/Packages/python-urlgrabber-3.9.1-8.el6.noarch.rpm http://mirror.ihug.co.nz/centos/6/os/$(uname -i)/Packages/python-pycurl-7.19.0-8.el6.$(uname -i).rpm http://mirror.ihug.co.nz/centos/6/os/$(uname -i)/Packages/rpm-python-4.8.0-19.el6.$(uname -i).rpm http://mirror.ihug.co.nz/centos/6/os/$(uname -i)/Packages/yum-3.2.29-22.el6.centos.noarch.rpm CentOS 5.7:
rpm
-Uvh --nodeps http://vault.centos.org/5.7/os/$(uname
-i)/CentOS/yum-fastestmirror-1.1.16-16.el5.centos.noarch.rpm
http://vault.centos.org/5.7/os/$(uname
-i)/CentOS/yum-metadata-parser-1.1.2-3.el5.centos.$(uname -i).rpm
rpm -Uvh http://vault.centos.org/5.7/os/$(uname -i)/CentOS/libxml2-2.6.26-2.1.12.$(uname -i).rpm http://vault.centos.org/5.7/os/$(uname -i)/CentOS/m2crypto-0.16-8.el5.$(uname -i).rpm http://vault.centos.org/5.7/os/$(uname -i)/CentOS/python-elementtree-1.2.6-5.$(uname -i).rpm http://vault.centos.org/5.7/os/$(uname -i)/CentOS/python-iniparse-0.2.3-4.el5.noarch.rpm http://vault.centos.org/5.7/os/$(uname -i)/CentOS/python-sqlite-1.1.7-1.2.1.$(uname -i).rpm http://vault.centos.org/5.7/os/$(uname -i)/CentOS/python-urlgrabber-3.1.0-6.el5.noarch.rpm http://vault.centos.org/5.7/updates/$(uname -i)/RPMS/rpm-python-4.4.2.3-22.el5_7.2.$(uname -i).rpm http://vault.centos.org/5.7/os/$(uname -i)/CentOS/yum-3.2.22-37.el5.centos.noarch.rpm CentOS 5.6:
rpm
-Uvh --nodeps http://vault.centos.org/5.6/os/$(uname
-i)/CentOS/yum-fastestmirror-1.1.16-14.el5.centos.1.noarch.rpm
http://vault.centos.org/5.6/os/$(uname
-i)/CentOS/yum-metadata-parser-1.1.2-3.el5.centos.$(uname -i).rpm
rpm -Uvh http://vault.centos.org/5.6/os/$(uname -i)/CentOS/libxml2-2.6.26-2.1.2.8.el5_5.1.$(uname -i).rpm http://vault.centos.org/5.6/os/$(uname -i)/CentOS/python-elementtree-1.2.6-5.$(uname -i).rpm http://vault.centos.org/5.6/os/$(uname -i)/CentOS/python-iniparse-0.2.3-4.el5.noarch.rpm http://vault.centos.org/5.6/os/$(uname -i)/CentOS/python-sqlite-1.1.7-1.2.1.$(uname -i).rpm http://vault.centos.org/5.6/os/$(uname -i)/CentOS/rpm-python-4.4.2.3-22.el5.$(uname -i).rpm http://vault.centos.org/5.6/os/$(uname -i)/CentOS/m2crypto-0.16-6.el5.8.$(uname -i).rpm http://vault.centos.org/5.6/os/$(uname -i)/CentOS/python-urlgrabber-3.1.0-6.el5.noarch.rpm http://vault.centos.org/5.6/os/$(uname -i)/CentOS/yum-3.2.22-33.el5.centos.noarch.rpm CentOS 5.5:
rpm
-Uvh --nodeps http://vault.centos.org/5.5/os/$(uname
-i)/CentOS/yum-fastestmirror-1.1.16-14.el5.centos.1.noarch.rpm
http://vault.centos.org/5.5/os/$(uname
-i)/CentOS/yum-metadata-parser-1.1.2-3.el5.centos.$(uname -i).rpm
rpm -Uvh http://vault.centos.org/5.5/updates/$(uname -i)/RPMS/libxml2-2.6.26-2.1.2.8.el5_5.1.$(uname -i).rpm http://vault.centos.org/5.5/os/$(uname -i)/CentOS/m2crypto-0.16-6.el5.6.$(uname -i).rpm http://vault.centos.org/5.5/os/$(uname -i)/CentOS/python-elementtree-1.2.6-5.$(uname -i).rpm http://vault.centos.org/5.5/os/$(uname -i)/CentOS/python-iniparse-0.2.3-4.el5.noarch.rpm http://vault.centos.org/5.5/os/$(uname -i)/CentOS/python-sqlite-1.1.7-1.2.1.$(uname -i).rpm http://vault.centos.org/5.5/os/$(uname -i)/CentOS/python-urlgrabber-3.1.0-5.el5.noarch.rpm http://vault.centos.org/5.5/updates/$(uname -i)/RPMS/rpm-python-4.4.2.3-20.el5_5.1.$(uname -i).rpm http://vault.centos.org/5.5/os/$(uname -i)/CentOS/yum-3.2.22-26.el5.centos.noarch.rpm |
|
VOS3000 Installation Manual
How to install VOS3000 soft switch.
1- Install CentOS 5.5 or latest.
2- Choose minimum installation
3- Choose Server mode only don’t install KDE or GNOME.
4- Run the following command
#yum update (to update the CentOS)
5- Better to install webmin to manage CentOS remotely.
# cd /var
# wget http://prdownloads.sourceforge.net/webadmin/webmin-1.530-1.noarch.rpm
# rpm -ivh webmin-1.530-1.noarch.rpm
After the installation open your browser and try to login i to webmin
http://youripaddress:10000
Login with root . and update the webmin and update the operating systems .
6- Disable the SELINUX mode
# vi /etc/sysconfig/selinux
---------------------------------------------------------------------------------------------------
# This file controls the state of SELinux on the system.
# SELINUX= can take one of these three values:
# enforcing - SELinux security policy is enforced.
# permissive - SELinux prints warnings instead of enforcing.
# disabled - SELinux is fully disabled.
SELINUX=disabled # SELINUXTYPE= type of policy in use. Possible values are:
# targeted - Only targeted network daemons are protected.
# strict - Full SELinux protection.
SELINUXTYPE=targeted
# SETLOCALDEFS= Check local definition changes
SETLOCALDEFS=0
------------------------------------------------------------------------------------------------
Save the file and exit
7 Check the iptables status of IPv4 and IPv6 to install VOS 3000 successfully disables the firewall
Follow the below command
# /etc/init.d/iptables status
This command will show IPtables is running or stop
# /etc/init.d/iptables save
This command will save the iptables (firewall rules)
# /etc/init.d/iptables stop
This command will stop the IPtables
# chkconfig iptables off
This Command will disable the iptables services
# /etc/init.d/ip6tables status
This command willl show IPtables is running or stop
# /etc/init.d/ip6tables save
This command will save the iptables (firewall rules)
# /etc/init.d/ip6tables stop
This command will stop the IPtables
# chkconfig ip6tables off
This Command will disable the iptables services
# ca /etc/issue
# cat /etc/issue
Reboot the server and check the IPtables is off.
# reboot
8-Install the dependency software’s for VOS 3000
# cd /usr
# tar xvf apache-tomcat-5.5.15.tar.gz
# rpm -ivh perl-DBI-1.40-5.i386.rpm
# rpm -ivh MySQL-server-community-5.0.51a-0.rhel4.i386.rpm
# rpm -ivh MySQL-client-community-5.0.51a-0.rhel4.i386.rpm
# rpm -ivh jdk-1_5_0_08-linux-i586.rpm
# rpm -ivh emp-2.1.1-5.noarch.rpm
# rpm -ivh mbx3000-2.1.1-5.i586.rpm
# rpm -ivh vos3000-2.1.1-5.i586.rpm
# rpm -ivh ivr-2.1.1-5.i586.rpm
Restart the VOS3000d Services
# /etc/init.d/vos3000d restart
# /etc/init.d/vos3000dall restart
Restart the MySQL services
# service mysql restart
Reboot the Server
Now VOS3000 Installation has done
Procedure of License Installation of VOS3000
VOS3000 License require the Server IP address and MAC address
To get the IP address and MAC Address follow below
# ifconfig
Link encap:Ethernet HWaddr 00:0C:29:27:03:FD
inet addr:10.31.7.13 Bcast:10.31.7.255 Mask:255.255.255.0
Create a directory for VOS3000 License
# cd /usr/kunshi
# mkdir license
# cd license
Copy the License file here and make it executable
# chmod 755 license.dat
Now restart the MySQL Services
# /etc/init.d/mysql restart
Restart the VOS3000 Services
# /etc/init.d/vos3000d
# /etc/init.d/vos3000d restart
# /etc/init.d/vos3000dall restart
# /etc/init.d/mbx3000d restart
Now change the MySQL root Password
# usr/bin/mysqladmin -u root password vos3000
MySQL Error: Client requested master to start replication from impossible position
Error reading packet from server: Client requested master to start replication from impossible position (server_errno=1236)
Start replication all over. Follow normal instructions on taking the main database down, record the master position, make a snapshot, copy it over to slave, start things back up, etc.
A more
Assmption: Lets assume that your slave was up-to-date with the master when things went sour. This should usually be the case on a properly-configured not-overly-loaded replication setup.
First, lets look at the master status on the master:
mysql> show master status;
+----------------+----------+--------------+------------------+
| File | Position | Binlog_do_db | Binlog_ignore_db |
+----------------+----------+--------------+------------------+
| box162-bin.014 | 29510700 | | |
+----------------+----------+--------------+------------------+
1 row in set (0.00 sec)
Okay, lets assume that when you rebooted the master or brought it back up after the power failure, that it will have started this new log, number 014.
My slave was stuck on number 013, and giving the "Client requested master to start replication from impossible position" error.
How to fix? Well, again, with the big assumption that the slave was generally up-to-date anyway, I simply went to the slave and did:
slave stop;
CHANGE MASTER TO MASTER_HOST='sunabc.net', MASTER_USER='repluser',MASTER_PASSWORD='replPass', MASTER_LOG_FILE='mysql-bin.000005', MASTER_LOG_POS=0
slave start;
And there we have it! The slave will start replicating on the new file. When power goes out and you have incomplete replication logs like this, we're really hoping that things are close enough in sync that this works.
Just do a "show slave status" on your slave, and make sure Slave_IO_Running and Slave_SQL_Running both say yes.
If you get errors about duplicate keys or other SQL inconsistency, then sorry, you were not as lucky this time. Do the normal backup.
Continue reading MySQL Error: Client requested master to start replication from impossible position
Got fatal error 1236: 'Client requested master to start replication from impossible position' from master when reading data from binary log
This might happen, for example, if there is a power failure on the master and it is unable to write out all the transactions to the replication log.
The proper way to fix it
Start replication all over. Follow normal instructions on taking the main database down, record the master position, make a snapshot, copy it over to slave, start things back up, etc.
A more lazy clever approach
Assmption: Lets assume that your slave was up-to-date with the master when things went sour. This should usually be the case on a properly-configured not-overly-loaded replication setup.
First, lets look at the master status on the master:
mysql> show master status;
+----------------+----------+--------------+------------------+
| File | Position | Binlog_do_db | Binlog_ignore_db |
+----------------+----------+--------------+------------------+
| box162-bin.014 | 29510700 | | |
+----------------+----------+--------------+------------------+
1 row in set (0.00 sec)
Okay, lets assume that when you rebooted the master or brought it back up after the power failure, that it will have started this new log, number 014.
My slave was stuck on number 013, and giving the "Client requested master to start replication from impossible position" error.
How to fix? Well, again, with the big assumption that the slave was generally up-to-date anyway, I simply went to the slave and did:
slave stop;
CHANGE MASTER TO MASTER_HOST='sunabc.net', MASTER_USER='repluser',MASTER_PASSWORD='replPass', MASTER_LOG_FILE='mysql-bin.000005', MASTER_LOG_POS=0
slave start;
And there we have it! The slave will start replicating on the new file. When power goes out and you have incomplete replication logs like this, we're really hoping that things are close enough in sync that this works.
Just do a "show slave status" on your slave, and make sure Slave_IO_Running and Slave_SQL_Running both say yes.
If you get errors about duplicate keys or other SQL inconsistency, then sorry, you were not as lucky this time. Do the normal backup.
RAID 0, RAID 1, RAID 5, RAID 10 Explained with Diagrams
RAID stands for Redundant Array of Inexpensive (Independent) Disks.
On most situations you will be using one of the following four levels of RAIDs.
In all the diagrams mentioned below:
Following are the key points to remember for RAID level 0.
Following are the key points to remember for RAID level 1.
Following are the key points to remember for RAID level 5.
Continue reading RAID 0, RAID 1, RAID 5, RAID 10 Explained with Diagrams
On most situations you will be using one of the following four levels of RAIDs.
- RAID 0
- RAID 1
- RAID 5
- RAID 10 (also known as RAID 1+0)
In all the diagrams mentioned below:
- A, B, C, D, E and F – represents blocks
- p1, p2, and p3 – represents parity
RAID LEVEL 0
Following are the key points to remember for RAID level 0.
- Minimum 2 disks.
- Excellent performance ( as blocks are striped ).
- No redundancy ( no mirror, no parity ).
- Don’t use this for any critical system.
RAID LEVEL 1
- Minimum 2 disks.
- Good performance ( no striping. no parity ).
- Excellent redundancy ( as blocks are mirrored ).
RAID LEVEL 5
Following are the key points to remember for RAID level 5.
- Minimum 3 disks.
- Good performance ( as blocks are striped ).
- Good redundancy ( distributed parity ).
- Best cost effective option providing both performance and redundancy. Use this for DB that is heavily read oriented. Write operations will be slow.
RAID LEVEL 10
Following are the key points to remember for RAID level 10.
- Minimum 4 disks.
- This is also called as “stripe of mirrors”
- Excellent redundancy ( as blocks are mirrored )
- Excellent performance ( as blocks are striped )
- If you can afford the dollar, this is the BEST option for any mission critical applications (especially databases).
Install RRDTool on Red Hat Enterprise Linux
RRD is the Acronym for Round Robin Database. RRD is a system to store
and display time-series data (i.e. network bandwidth, machine-room
temperature, server load average). It stores the data in a very compact
way that will not expand over time, and it presents useful graphs by
processing the data to enforce a certain data density. It can be used
either via simple wrapper scripts (from shell or Perl) or via frontends
that poll network devices and put a friendly user interface on it.
Sample output:
Untar tar ball, enter:
Type the following commands:
Sample output:
Continue reading Install RRDTool on Red Hat Enterprise Linux
Installing RRDTool on RHEL
In order to install RRDTool on Red Hat Enterprise Linux / CentOS Linux 64 bit version you need to install few development tools and libraries.Step # 1: Install required dependencies
Login as root and type the following command:# yum install cairo-devel libxml2-devel pango-devel pango libpng-devel freetype freetype-devel libart_lgpl-devel Sample output:
Loading "rhnplugin" plugin Loading "security" plugin rhel-x86_64-server-vt-5 100% |=========================| 1.4 kB 00:00 rhn-tools-rhel-x86_64-ser 100% |=========================| 1.2 kB 00:00 rhel-x86_64-server-5 100% |=========================| 1.4 kB 00:00 Setting up Install Process Parsing package install arguments Package libxml2-devel - 2.6.26-2.1.2.1.x86_64 is already installed. Package libxml2-devel - 2.6.26-2.1.2.1.i386 is already installed. Package pango - 1.14.9-3.el5.i386 is already installed. Package pango - 1.14.9-3.el5.x86_64 is already installed. Package freetype - 2.2.1-20.el5_2.i386 is already installed. Package freetype - 2.2.1-20.el5_2.x86_64 is already installed. Resolving Dependencies --> Running transaction check ---> Package libart_lgpl-devel.x86_64 0:2.3.17-4 set to be updated ---> Package pango-devel.i386 0:1.14.9-3.el5 set to be updated --> Processing Dependency: libXft-devel for package: pango-devel --> Processing Dependency: libXrender-devel for package: pango-devel --> Processing Dependency: libXext-devel for package: pango-devel --> Processing Dependency: libX11-devel for package: pango-devel --> Processing Dependency: fontconfig-devel >= 2.0 for package: pango-devel ---> Package pango-devel.x86_64 0:1.14.9-3.el5 set to be updated ---> Package freetype-devel.x86_64 0:2.2.1-20.el5_2 set to be updated ---> Package libpng-devel.i386 2:1.2.10-7.1.el5_0.1 set to be updated ---> Package cairo-devel.x86_64 0:1.2.4-5.el5 set to be updated ---> Package libpng-devel.x86_64 2:1.2.10-7.1.el5_0.1 set to be updated ---> Package cairo-devel.i386 0:1.2.4-5.el5 set to be updated ---> Package libart_lgpl-devel.i386 0:2.3.17-4 set to be updated --> Processing Dependency: libart_lgpl_2.so.2 for package: libart_lgpl-devel ---> Package freetype-devel.i386 0:2.2.1-20.el5_2 set to be updated --> Running transaction check ---> Package libXrender-devel.i386 0:0.9.1-3.1 set to be updated --> Processing Dependency: xorg-x11-proto-devel for package: libXrender-devel ---> Package libXft-devel.i386 0:2.1.10-1.1 set to be updated ---> Package libX11-devel.i386 0:1.0.3-9.el5 set to be updated --> Processing Dependency: libXdmcp-devel for package: libX11-devel --> Processing Dependency: libXau-devel for package: libX11-devel ---> Package fontconfig-devel.i386 0:2.4.1-7.el5 set to be updated ---> Package libart_lgpl.i386 0:2.3.17-4 set to be updated ---> Package libXext-devel.i386 0:1.0.1-2.1 set to be updated --> Running transaction check ---> Package xorg-x11-proto-devel.i386 0:7.1-9.fc6 set to be updated --> Processing Dependency: mesa-libGL-devel for package: xorg-x11-proto-devel ---> Package libXdmcp-devel.i386 0:1.0.1-2.1 set to be updated ---> Package libXau-devel.i386 0:1.0.1-3.1 set to be updated --> Running transaction check ---> Package mesa-libGL-devel.i386 0:6.5.1-7.5.el5 set to be updated --> Finished Dependency Resolution Dependencies Resolved ============================================================================= Package Arch Version Repository Size ============================================================================= Installing: libart_lgpl-devel x86_64 2.3.17-4 rhel-x86_64-server-5 21 k libart_lgpl-devel i386 2.3.17-4 rhel-x86_64-server-5 21 k pango-devel i386 1.14.9-3.el5 rhel-x86_64-server-5 280 k pango-devel x86_64 1.14.9-3.el5 rhel-x86_64-server-5 281 k Installing for dependencies: cairo-devel x86_64 1.2.4-5.el5 rhel-x86_64-server-5 131 k cairo-devel i386 1.2.4-5.el5 rhel-x86_64-server-5 130 k fontconfig-devel i386 2.4.1-7.el5 rhel-x86_64-server-5 168 k freetype-devel x86_64 2.2.1-20.el5_2 rhel-x86_64-server-5 151 k freetype-devel i386 2.2.1-20.el5_2 rhel-x86_64-server-5 151 k libX11-devel i386 1.0.3-9.el5 rhel-x86_64-server-5 665 k libXau-devel i386 1.0.1-3.1 rhel-x86_64-server-5 11 k libXdmcp-devel i386 1.0.1-2.1 rhel-x86_64-server-5 7.6 k libXext-devel i386 1.0.1-2.1 rhel-x86_64-server-5 57 k libXft-devel i386 2.1.10-1.1 rhel-x86_64-server-5 16 k libXrender-devel i386 0.9.1-3.1 rhel-x86_64-server-5 8.9 k libart_lgpl i386 2.3.17-4 rhel-x86_64-server-5 76 k libpng-devel i386 2:1.2.10-7.1.el5_0.1 rhel-x86_64-server-5 182 k libpng-devel x86_64 2:1.2.10-7.1.el5_0.1 rhel-x86_64-server-5 186 k mesa-libGL-devel i386 6.5.1-7.5.el5 rhel-x86_64-server-5 465 k xorg-x11-proto-devel i386 7.1-9.fc6 rhel-x86_64-server-5 247 k Transaction Summary ============================================================================= Install 20 Package(s) Update 0 Package(s) Remove 0 Package(s) Total download size: 3.2 M Is this ok [y/N]: Downloading Packages: (1/20): libXext-devel-1.0 100% |=========================| 57 kB 00:00 (2/20): freetype-devel-2. 100% |=========================| 151 kB 00:00 (3/20): libXau-devel-1.0. 100% |=========================| 11 kB 00:00 (4/20): libart_lgpl-devel 100% |=========================| 21 kB 00:00 (5/20): libart_lgpl-2.3.1 100% |=========================| 76 kB 00:00 (6/20): cairo-devel-1.2.4 100% |=========================| 130 kB 00:00 (7/20): libpng-devel-1.2. 100% |=========================| 186 kB 00:00 (8/20): cairo-devel-1.2.4 100% |=========================| 131 kB 00:00 (9/20): fontconfig-devel- 100% |=========================| 168 kB 00:00 (10/20): mesa-libGL-devel 100% |=========================| 465 kB 00:01 (11/20): libXdmcp-devel-1 100% |=========================| 7.6 kB 00:00 (12/20): libpng-devel-1.2 100% |=========================| 182 kB 00:00 (13/20): libX11-devel-1.0 100% |=========================| 665 kB 00:02 (14/20): freetype-devel-2 100% |=========================| 151 kB 00:00 (15/20): libXft-devel-2.1 100% |=========================| 16 kB 00:00 (16/20): pango-devel-1.14 100% |=========================| 281 kB 00:01 (17/20): pango-devel-1.14 100% |=========================| 280 kB 00:01 (18/20): libXrender-devel 100% |=========================| 8.9 kB 00:00 (19/20): libart_lgpl-deve 100% |=========================| 21 kB 00:00 (20/20): xorg-x11-proto-d 100% |=========================| 247 kB 00:01 Running rpm_check_debug Running Transaction Test Finished Transaction Test Transaction Test Succeeded Running Transaction Installing: libart_lgpl ####################### [ 1/20] Installing: freetype-devel ####################### [ 2/20] Installing: fontconfig-devel ####################### [ 3/20] Installing: libpng-devel ####################### [ 4/20] Installing: libXau-devel ####################### [ 5/20] Installing: libart_lgpl-devel ####################### [ 6/20] Installing: libart_lgpl-devel ####################### [ 7/20] Installing: libpng-devel ####################### [ 8/20] Installing: freetype-devel ####################### [ 9/20] Installing: xorg-x11-proto-devel ####################### [10/20] Installing: libX11-devel ####################### [11/20] Installing: libXrender-devel ####################### [12/20] Installing: libXft-devel ####################### [13/20] Installing: cairo-devel ####################### [14/20] Installing: libXext-devel ####################### [15/20] Installing: pango-devel ####################### [16/20] Installing: pango-devel ####################### [17/20] Installing: libXdmcp-devel ####################### [18/20] Installing: mesa-libGL-devel ####################### [19/20] Installing: cairo-devel ####################### [20/20] Installed: libart_lgpl-devel.x86_64 0:2.3.17-4 libart_lgpl-devel.i386 0:2.3.17-4 pango-devel.i386 0:1.14.9-3.el5 pango-devel.x86_64 0:1.14.9-3.el5 Dependency Installed: cairo-devel.x86_64 0:1.2.4-5.el5 cairo-devel.i386 0:1.2.4-5.el5 fontconfig-devel.i386 0:2.4.1-7.el5 freetype-devel.x86_64 0:2.2.1-20.el5_2 freetype-devel.i386 0:2.2.1-20.el5_2 libX11-devel.i386 0:1.0.3-9.el5 libXau-devel.i386 0:1.0.1-3.1 libXdmcp-devel.i386 0:1.0.1-2.1 libXext-devel.i386 0:1.0.1-2.1 libXft-devel.i386 0:2.1.10-1.1 libXrender-devel.i386 0:0.9.1-3.1 libart_lgpl.i386 0:2.3.17-4 libpng-devel.i386 2:1.2.10-7.1.el5_0.1 libpng-devel.x86_64 2:1.2.10-7.1.el5_0.1 mesa-libGL-devel.i386 0:6.5.1-7.5.el5 xorg-x11-proto-devel.i386 0:7.1-9.fc6 Complete!
Step # 2: Download latest rrdtool tar ball
Type the following commands:# cd /opt/
# wget http://oss.oetiker.ch/rrdtool/pub/rrdtool-1.3.1.tar.gzUntar tar ball, enter:
# tar -zxvf rrdtool-1.3.1.tar.gz Step #3: Compile and install rrdtool
You need to set PKG_CONFIG_PATH, enter:# export PKG_CONFIG_PATH=/usr/lib/pkgconfig/Type the following commands:
# ./configureSample output:
config.status: executing default-1 commands
config.status: executing intltool commands
config.status: executing default commands
config.status: executing po/stamp-it commands
checking in... and out again
ordering CD from http://tobi.oetiker.ch/wish .... just kidding ;-)
----------------------------------------------------------------
Config is DONE!
With MMAP IO: yes
Static programs: no
Perl Modules: perl_piped perl_shared
Perl Binary: /usr/bin/perl
Perl Version: 5.8.8
Perl Options: PREFIX=/usr/local/rrdtool-1.3.1 LIB=/usr/local/rrdtool-1.3.1/lib/perl/5.8.8
Ruby Modules:
Ruby Binary: no
Ruby Options: sitedir=$(DESTDIR)NONE/lib/ruby
Build Tcl Bindings: no
Build Python Bindings: yes
Build rrdcgi: yes
Build librrd MT: yes
Link with libintl: yes
Libraries: -lxml2 -lcairo -lcairo -lcairo -lm -lcairo -lpng12 -lpangocairo-1.0 -lpango-1.0 -lcairo -lgobject-2.0 -lgmodule-2.0 -ldl -lglib-2.0
Type 'make' to compile the software and use 'make install' to
install everything to: /usr/local/rrdtool-1.3.1.
... that wishlist is NO JOKE. If you find RRDtool useful
make me happy. Go to http://tobi.oetiker.ch/wish and
place an order.
-- Tobi Oetiker
----------------------------------------------------------------
Now compile and install RRDTool on RHEL:# make
# make install
# cd /usr/local/
# ln -s rrdtool-1.3.1/ rrdtool/
# cd rrdtool
# ls -l How to Root Your Samsung Galaxy Ace
If you own a Samsung Galaxy Ace S5830 running on Android 2.3.5 Gingerbread DDKQ5 or DDKQ6 version, you can now easily root your device. If you are unsure what version your phone is running, you can verify by heading to Settings > About Phone > Firmware Version, in which you can find valuable information on what type of firmware version your device has.
What is Rooting?
For those of you who are not familiar with rooting, it is like jailbreaking your phone to support neat new features normally not found on a smartphone. There are many benefits you can have once you gain root access on your device. For example, you can make your phone run faster, install custom ROMs, and install (sideload) applications from third-party sources.Along with great functionalities and features rooting has to offer, it also has some downsides. Once you root your device, you are also (possibly) voiding its warranty. Although, there is usually the option of unrooting your device by updating it with a stock ROM. Overall, rooting can be a win-win situation.
Prerequisites
- Just in case your phone data, call log, text messages, and media files get erased in the process, you need to backup those files as a precautionary measure.
- In order for the rooting process to begin, it is highly suggested that you need to at least charge your phone to 60%.
- You also need to enable USB Debugging on your phone. This can be enabled by heading to Settings > Applications > Development > USB Debugging.
- Lastly, close all potentially conflicting applications on your computer such as antivirus software, Samsung Kies PC Suite, and firewall software as they tend to disrupt or block the rooting process. If you do have other unnecessary applications that cause your phone delays, you should uninstall them or remove them as well.
Rooting Instructions
- Download the latest Galaxy ACE Rooting Package to your computer. Get the file here (about 925 KB).
- Connect your phone to your computer via USB cable.
- Copy the downloaded ZIP file to your phone’s SD card without renaming or modifying the file.
- Reboot into recovery mode. Turn off your phone. Then, simultaneously press and hold the Volume Up + OK button, and press the Power button.
- Your phone will boot to the recovery mode screen. From here, choose “Install zip from SD Card” and select “Choose Zip from SD”.
- Using the Volume Up and Volume Down keys, locate the ZIP file that you just copied to your SD card (the one named “upd_1.zip”). Press the Power button to select it.
- Wait for about 5 – 10 minutes for the rooting process to finish.
- Once the rooting process is done, your phone will automatically reboot. If it fails to do so, head back to the main menu by selecting “++++ Go Back ++++” and select “Reboot System Now” to manually reboot your phone.
How to do a "printscreen" with a MacBook/MacBook Pro on the Windows side
This is the case: You have a MacBook or a MacBook Pro (I supose it should work on a iMac too), and for some reason you have Windows(r) installed and want to take a screenshot (printscreen).
This was tested with BootCamp 2.0
Since the MacBook/MacBook Pro don't have a "printscreen" key you shoul try this:Shift + Fn + F11 (If your functions key controls the hardware)
Shift + F11 (If your function keys bahaves as normal functions keys)
If you want take a screenshot of the active window jus add the Alt key.
Alt + Shift + Fn + F11 (If your functions key controls the hardware)
Alt + Shift + F11 (If your function keys bahaves as normal functions keys)
Document Actions
How Block IPs Using Windows IPSec
Here is something that I would like to share with every one and quite rare to find out. This tutorial will show how to block IPs on Windows server without firewall using IPSec:
Click 'Start' > 'Run' >type 'MMC' press ok.
In the console click > 'File' > 'Add/Remove Snap in'
In the 'Standalone Tab' click The 'add' button
Seclect 'IP Security Policy Managment' > 'ADD' > 'Local Computer' > 'finish' > 'close' > 'ok'
You should now be back to the console.
In the left frame right click 'IP security policies on local computer' > 'Create IP security policy'
Click Next and then name your policy 'Block IP' and type a description.
Click 'Next' then leave 'activate' ticked then click 'Next'
leave the 'edit properties ticked and click 'Finish'
You should now have the properties window open.
Click 'ADD' then click 'Next' to continue.
Leave 'This rule does not specify a tunnel' selected and click 'next'
Leave 'all network connections' selected and click 'next'
You should now be on the IP filter list. You need to create a new filter, so dont select any of the default ones. Click 'ADD'
Type a Name for your list, call it 'IP block list'
Type a description in, can be same as name.
Click 'ADD' then click 'Next' to continue.
In the description box type a description. As its the first IP you are blocking call it 'IP1' or 'IP Range 1'
Leave ticked the 'Mirrored. Match packets with the exact opposite source and destination addresses'
Click 'Next'
The 'Source address' should be left as 'My IP address' click 'Next'
You can now select 'A Specific IP address' or 'A Specific Subnet' for the Destination address.
Type in the IP address you want to block and if blocking a subnet type in the subnet block. Click 'next'
Leave the protocol type as 'Any' and click 'Next' and then 'Finish'
You have now blocked your first IP or IP range.
Continue reading How Block IPs Using Windows IPSec
Click 'Start' > 'Run' >type 'MMC' press ok.
In the console click > 'File' > 'Add/Remove Snap in'
In the 'Standalone Tab' click The 'add' button
Seclect 'IP Security Policy Managment' > 'ADD' > 'Local Computer' > 'finish' > 'close' > 'ok'
You should now be back to the console.
In the left frame right click 'IP security policies on local computer' > 'Create IP security policy'
Click Next and then name your policy 'Block IP' and type a description.
Click 'Next' then leave 'activate' ticked then click 'Next'
leave the 'edit properties ticked and click 'Finish'
You should now have the properties window open.
Click 'ADD' then click 'Next' to continue.
Leave 'This rule does not specify a tunnel' selected and click 'next'
Leave 'all network connections' selected and click 'next'
You should now be on the IP filter list. You need to create a new filter, so dont select any of the default ones. Click 'ADD'
Type a Name for your list, call it 'IP block list'
Type a description in, can be same as name.
Click 'ADD' then click 'Next' to continue.
In the description box type a description. As its the first IP you are blocking call it 'IP1' or 'IP Range 1'
Leave ticked the 'Mirrored. Match packets with the exact opposite source and destination addresses'
Click 'Next'
The 'Source address' should be left as 'My IP address' click 'Next'
You can now select 'A Specific IP address' or 'A Specific Subnet' for the Destination address.
Type in the IP address you want to block and if blocking a subnet type in the subnet block. Click 'next'
Leave the protocol type as 'Any' and click 'Next' and then 'Finish'
You have now blocked your first IP or IP range.
How to Set Up Virtual Hosting on Apache
If you are running an Apache Web server on a DSL or faster link, you can become a hosting provider for other people. You can even host their domains, without needing an IP for each domain. This is called virtual hosting, and you'd be surprised at how easy it is. Remember, some access providers have rules against running hosting services, check your hosting agreement for more information.
Register a Domain
The first thing that needs to happen is you need to register a domain at Internic or Register.com. Follow the instructions at these sites (links on the right), to register your new domain. If you're creating this for a customer, you can have them register the domain or you can do it yourself.
Domain Name Service
This is the hardest part. If you don't host your own DNS, you'll need to contact your hosting provider to have the new domain added to the DNS server. If you're hosting your own DNS this consists of:
- edit Bind or NameD or DNS to add the new domain name
- point it to the IP of your virtual hosting server
- restart your DNS service
Apache Configuration
Once you have the DNS pointing to your virtual domain server, you need to tell your Web server where to find the Web files for the domain. The way Apache works, if you have set up virtual domains, the first domain entered is the default. This is the directory that will be displayed when a virtual domain is not listed in the configuration. (In other words, if the DNS entry made above sends the URL to your IP, but you don't have the virtual host in your httpd.conf file.)
An Example
You have bought the domain www.adogslife.com and you want to host it at the hosting service with the IP 10.1.1.1 (which you also own).
DNS is set up to point to that IP.
Now you must edit your Apache httpd.conf file:
- Go to the section of the httpd.conf file on Virtual hosting (sometimes it's in srm.conf)
- Make sure that the NameVirtualHost points to your IP:NameVirtualHost 10.1.1.1
- The first virtual host entry should be your default domain:
ServerName www.defaultdomain.com
DocumentRoot /www/domain - Then list the new domain, with any options you'd like to add:
ServerName www.adogslife.com
DocumentRoot /www/dogslife
ErrorLog logs/adogslife.com-error_log
TransferLog logs/adogslife.com-access_log
Note, I added two lines to the second virtual host. These allow you to separate out the Error and Transfer logs for the new domain from your default domain. If you are going to host virtual domains for other people, they will almost certainly want their server logs, and this makes it easy to provide that to them as well.
How can I install PHP5 under IIS 6.0?
Download the latest PHP version for Windows from http://www.php.net/downloads.php, right-click on the PHP folder, and select "Extract All..."
Select "Next"
Choose C:\Program Files\PHP5 as extract directory and click on "Next"
Uncheck "Show extracted files" and click on "Finish"
Launch the "Internet Information Services (IIS) Manager" from the start menu. You need to install IIS in case this option is not available.
Right-click on "Website" and select "Properties"
Select the "Home Directory" tab and choose "Configuration"
Choose "Add"
Add "C:\Program Files\PHP5\php5isapi.dll" (including quotes) to "Executable" and add .php as extension. Then limit the verbs to GET,HEAD,POST,TRACE and click on OK
Now choose the "Documents" tab and select "Add"
Enter index.php and click on OK
Now, you can change the priority of your index.php with the "Move Up" button. This is only necessary if you run primary a PHP based website
Finally, select Web Service Extensions on the left side and choose "Add a new Web service extension"
Select "Add" and enter as path C:\Program Files\PHP5\php5isapi.dll and click on OK
Then enter php5 as extension name and check "Set extension status to Allowed". Then click on OK to enable this extension
Copy C:\Program Files\PHP5\php.ini-dist to C:\WINDOWS\php.ini and restart IIS
Then create the following php file with Notepad:
Save this file under C:\Inetpub\wwwroot\test.php
Now launch Internet Explorer and go to http://localhost/test.php . You should see the PHP info page if your PHP5 installation was successfully.
| |