Sunday, October 9, 2011

How-To: Installing Smokeping on CentOS 5.5

yum update
# rpm -Uhv
# yum install httpd
# yum install rrdtool
# yum install fping
# yum install echoping
# yum install curl
# yum install perl perl-Net-Telnet perl-Net-DNS perl-LDAP perl-libwww-perl perl-RadiusPerl perl-IO-Socket-SSL perl-Socket6 perl-CGI-SpeedyCGI

# wget
# tar zxvf smokeping-2.4.1.tar.gz
# mv smokeping-2.4.1 /opt/smokeping
# cd /opt/smokeping

# cd bin/
# cp smokeping.dist smokeping
# cd ../htdocs/
# cp smokeping.cgi.dist smokeping.cgi
# cp tr.cgi.dist tr.cgi
# cd ../etc/
# cp config.dist config
# cp basepage.html.dist basepage.html
# cp smokemail.dist smokemail
# cp tmail.dist tmail
# cp smokeping_secrets.dist smokeping_secrets
# chmod 600 /opt/smokeping/etc/smokeping_secrets

# vi /opt/smokeping/bin/smokeping

Hard Drives IOPS

Found and interesting topic over the weekend. A topic which most of us overlook during the design of a storage infrastructure.

We all do concern about the speed if the data transfer between storage and host, the network bandwidth, and that RAID configuration used, while we always forgot about the IOPS.

For some of us out there who wondering what is IOPS, "IOPS (Input/Output Operations Per Second, pronounced i-ops) is a common performance measurement used to benchmark computer storage devices like hard disk drives (HDD), solid state drives (SSD), and storage area networks (SAN). As with any benchmark, IOPS numbers published by storage device manufacturers do not guarantee real-world application performance" - Wikipedia (on layman term)

The table I found below to remind myself of the ball park IOPS figure of various type of common hard drives:

7,200 rpm HDD~75-100 IOPS[2]SATA 3 Gb/s
10,000 rpHDD~125-150 IOPS[2]SATA 3 Gb/s
15,000 rpHDD~175-210 IOPS [2]SAS
Simple SLSSD~400 IOPS[citation needed]SATA 3 Gb/s
Intel X25-SSD~8,600 IOPS[11]SATA 3 Gb/s
Intel X25-SSD~5,000 IOPS[13]SATA 3 Gb/s
G.Skill PhSSD~20,000 IOPS[citation needed]SATA 3 Gb/s
OCZ VerteSSDUp to 60,000 IOPS[citation needed]SATA 6 Gb/s
Texas MeSSD120,000+ Random Read/Write IOPS[17]PCIe
Fusion-io SSD140,000 Read IOPS, 135,000 Write IOPS [18]PCIe
Virident SSSD320,000 sustained READ IOPS using 4KB blocks and 200,000 sustained WRITE IOPS using 4KB blocks [19]PCIe
OCZ RevoSSD200,000 Random Write 4K IOPS [21]PCIe
Fusion-ioSSD250,000+ IOPS [22]PCIe
Violin MeSSD250,000+ Random Read/Write IOPS[23]PCIe /FC/Infiniband/iSCSI
DDRdrive SSD300,000+ (512B Random Read IOPS) and 200,000+ (512B Random Write IOPS)[24][25][26][27]PCIe
OCZ SinglSSDUp to 500,000 IOPS [28]PCIe
Texas MeSSD600,000+ Random Read/Write IOPS[29]PCIe
Texas MeSSD1,000,000+ Random Read/Write IOPS[30]FC / InfiniBand
Fusion-ioSSD1,180,000+ Random Read/Write IOPS[31]PCIe
OCZ 2x SuSSDUp to 1,200,000 IOPS[28]PCIe

Saturday, June 18, 2011

How-To: Chromium for BackTrack 5

To install Google Chrome Browser on BackTrack 5 :
# apt-get install chromium-browser

Upon installation, you can execute the Chromium Browser from
'KDE -> Internet -> Chromium Web Browser'

Soon you will hit to this error :

By default, the Chromium Browser could be run with 'root' privileges. This is predefined by developers of Google Chrome.

You need a workaround now.

Go to this directory:
cd /usr/lib/chromium-browser

Edit the Chromium-Browser with 'hexedit'
#hexedit --color Chromium-Browser

You start of on the HEX mode. Hit [TAB] to toggle between HEX and ASCII mode.

On the ASCII mode, hit [CTRL + s] to search 'geteuid'

Edit the 'geteuid' string to become 'getppid'

Hit [CTRL + x] to save change

Th Chromium Browser will now run with 'root' privileges.