<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"><channel><title>LINICKX.com</title><link>https://www.linickx.com/</link><description></description><lastBuildDate>Wed, 16 May 2012 14:39:00 +0100</lastBuildDate><item><title>apc.php for rhel / centos</title><link>https://www.linickx.com/apc-php-for-rhel-centos</link><description>&lt;p&gt;Note to self: The apc.php (&lt;em&gt;script for monitroing apc performance&lt;/em&gt;) is
stored in - &lt;code&gt;/usr/share/doc/php-pecl-apc-3.1.3p1&lt;/code&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">nick</dc:creator><pubDate>Wed, 16 May 2012 14:39:00 +0100</pubDate><guid isPermaLink="false">tag:www.linickx.com,2012-05-16:apc-php-for-rhel-centos</guid><category>centos</category><category>Enterprise Linux</category><category>Linux</category><category>PHP</category></item><item><title>5 Minute CentOS/RHEL VPN</title><link>https://www.linickx.com/5-minute-centosrhel-vpn</link><description>&lt;p&gt;I'm looking at running two servers on EC2; as we all know the most
important thing about running services in the cloud is &lt;strong&gt;encryption&lt;/strong&gt;!&lt;/p&gt;
&lt;p&gt;Whilst googling on how to setup a host-to-host IPSEC VPN I was surprised
at how easy it is...&lt;/p&gt;
&lt;p&gt;On Host1 (192.168.56.101)...&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;#!/bin/bash
[root@CentOS1 ~]# cat /etc/sysconfig/network-scripts/ifcfg-ipsec1 
DST=192.168.56.102
TYPE=IPSEC
ONBOOT=no
IKE_METHOD=PSK
[root@CentOS1 ~]#
[root@CentOS1 ~]# cat /etc/sysconfig/network-scripts/keys-ipsec1 
IKE_PSK=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
[root@CentOS1 ~]#
[root@CentOS1 ~]# ifup ipsec1
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;On host2 (192.168.56.102)...&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;#!/bin/bash
[root@CentOS2 ~]# cat /etc/sysconfig/network-scripts/ifcfg-ipsec1 
DST=192.168.56.101
TYPE=IPSEC
ONBOOT=no
IKE_METHOD=PSK
[root@CentOS2 ~]#
[root@CentOS2 ~]# cat /etc/sysconfig/network-scripts/keys-ipsec1 
IKE_PSK=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
[root@CentOS2 ~]#
[root@CentOS2 ~]#ifup ipsec1
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;... done!!!&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;#!/bin/bash
[root@CentOS1 ~]# tcpdump -n -i eth1 host 192.168.56.102
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth1, link-type EN10MB (Ethernet), capture size 96 bytes
09:46:37.306292 IP 192.168.56.101 &amp;gt; 192.168.56.102: AH(spi=0x0aff2b10,seq=0x203): ESP(spi=0x00a0a3cc,seq=0x203), length 84
09:46:37.310197 IP 192.168.56.102 &amp;gt; 192.168.56.101: AH(spi=0x09f82154,seq=0x203): ESP(spi=0x098f0ff9,seq=0x203), length 68
09:46:38.175048 IP 192.168.56.101 &amp;gt; 192.168.56.102: AH(spi=0x0aff2b10,seq=0x204): ESP(spi=0x00a0a3cc,seq=0x204), length 84
09:46:38.179017 IP 192.168.56.102 &amp;gt; 192.168.56.101: AH(spi=0x09f82154,seq=0x204): ESP(spi=0x098f0ff9,seq=0x204), length 68
09:46:39.313583 IP 192.168.56.101 &amp;gt; 192.168.56.102: AH(spi=0x0aff2b10,seq=0x205): ESP(spi=0x00a0a3cc,seq=0x205), length 84
09:46:39.316427 IP 192.168.56.102 &amp;gt; 192.168.56.101: AH(spi=0x09f82154,seq=0x205): ESP(spi=0x098f0ff9,seq=0x205), length 68

6 packets captured
6 packets received by filter
0 packets dropped by kernel
[root@CentOS1 ~]#
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Now this is a simple IKE pre-shared key vpn, you might want to google
for using certificates for stronger authentication, you can also edit
/etc/racoon/racoon.conf to change your IPSEC parameters.&lt;/p&gt;
&lt;p&gt;Reference:
&lt;a href="http://www.centos.org/docs/5/html/Deployment_Guide-en-US/ch-vpn.htm"&gt;http://www.centos.org/docs/5/html/Deployment_Guide-en-US/ch-vpn.html&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;UPDATE: To make this work in EC2, &lt;a href="https://www.linickx.com/archives/3195/centosredhat-ipsec-and-ec2"&gt;you need to enable NAT-T see my
hack
here&lt;/a&gt;!&lt;/strong&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">nick</dc:creator><pubDate>Sun, 23 Jan 2011 09:51:00 +0000</pubDate><guid isPermaLink="false">tag:www.linickx.com,2011-01-23:5-minute-centosrhel-vpn</guid><category>centos</category><category>Enterprise Linux</category><category>Security</category><category>vpn</category></item><item><title>Smolt RPM for CentOS, RHEL, etc</title><link>https://www.linickx.com/smolt-rpm-for-centos-rhel-etc</link><description>&lt;p&gt;I after installing Fedora7 I thought I'd take a look at &lt;a href="http://smolt.fedoraproject.org/stats"&gt;the
stats&lt;/a&gt; the project had gathered, I
saw some centos devices, but couldn't find a rpm.&lt;/p&gt;
&lt;p&gt;I've had a go at building one, it mostly works (&lt;a href="http://smolt.fedoraproject.org/show?UUID=251cf847-28b3-4d33-bb27-9fa6aecb5e61"&gt;this is my nagios
box&lt;/a&gt;),
it's a rebuild of the f7 source, I have to frig about with the spec
file, so I've published &lt;a href="https://www.linickx.com/files/rpm/whitebox/4/SRPMS/smolt-0.9.8.1-1.src.rpm"&gt;my source rpm
here&lt;/a&gt;,
search for Nick in the .spec file, you'll see my bodge.&lt;/p&gt;
&lt;p&gt;The smolt rpms are in &lt;a href="https://www.linickx.com/files/rpm/linickx-whitebox.repo"&gt;my yum
repo&lt;/a&gt;, feel free
to download the packages and have a go.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://www.linickx.com/files/rpm/whitebox/4/i386/smolt-0.9.8.1-1.noarch.rpm"&gt;smolt-0.9.8.1-1.noarch.rpm&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;s&lt;a href="https://www.linickx.com/files/rpm/whitebox/4/i386/smolt-firstboot-0.9.8.1-1.noarch.rpm"&gt;molt-firstboot-0.9.8.1-1.noarch.rpm&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.linickx.com/files/rpm/whitebox/4/i386/smolt-gui-0.9.8.1-1.noarch.rpm"&gt;smolt-gui-0.9.8.1-1.noarch.rpm&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.linickx.com/files/rpm/whitebox/4/i386/smolt-server-0.9.8.1-1.noarch.rpm"&gt;smolt-server-0.9.8.1-1.noarch.rpm&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">nick</dc:creator><pubDate>Fri, 06 Jul 2007 10:00:00 +0100</pubDate><guid isPermaLink="false">tag:www.linickx.com,2007-07-06:smolt-rpm-for-centos-rhel-etc</guid><category>centos</category><category>Enterprise Linux</category><category>Linux</category><category>redhat</category><category>rpm</category><category>smolt</category></item><item><title>Extra Packages for Enterprise Linux... CentOS !</title><link>https://www.linickx.com/extra-packages-for-enterprise-linux-centos</link><description>&lt;p&gt;Why has it taken me so long to spot this ? Looks like this draft was
written on the 13th May, if I hadn't have been just about to download
&lt;a href="http://fedoraproject.org/wiki/"&gt;FC7&lt;/a&gt; then I'd have missed it !&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;a href="http://fedoraproject.org/wiki/EPEL"&gt;EPEL - Fedora Project Wiki&lt;/a&gt;&lt;br /&gt;
 EPEL is a volunteer-based community effort from the Fedora project to
create a repository of high-quality add-on packages that complement
the Fedora-based Red Hat Enterprise Linux (RHEL) and its compatible
spinoffs like CentOS or Scientific Linux.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;About time, and thank you redhat/fedora, want fedora extra packages in
centos, then install this
&lt;a href="http://download.fedora.redhat.com/pub/epel/5/i386/repoview/epel-release.html"&gt;epel-release&lt;/a&gt;
&lt;a href="http://download.fedora.redhat.com/pub/epel/5/i386/epel-release-5-2.noarch.rpm"&gt;.rpm&lt;/a&gt;
frickin' sweet ! :cool:&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">nick</dc:creator><pubDate>Sun, 03 Jun 2007 17:54:00 +0100</pubDate><guid isPermaLink="false">tag:www.linickx.com,2007-06-03:extra-packages-for-enterprise-linux-centos</guid><category>Blog</category><category>centos</category><category>Enterprise Linux</category><category>epel</category><category>Fedora</category><category>fedora extras</category><category>Linux</category></item><item><title>Intel 3945ABG Wireless / WiFi Card on CentOS 5</title><link>https://www.linickx.com/intel-3945abg-wireless-wifi-card-on-centos-5</link><description>&lt;p&gt;I've taken to using CentOS on my servers, and fedora on my Laptop. New
job, means new laptop, and to avoid fedora update hell, I thought I'd
try CentOS on my laptop.&lt;/p&gt;
&lt;p&gt;All seems good other than my wifi card not being detected, and for some
reason googling for "&lt;a href="http://www.google.com/search?q=%22centos+5%22+intel+3945"&gt;centos 5 intel
3945&lt;/a&gt;" didn't
provide a working anserwer, actually I found the answer by googling for
"&lt;a href="http://www.google.com/search?q=Supplementary+disc+%22centos+5%22"&gt;supplementary disk centos
5&lt;/a&gt;"
which finds &lt;a href="http://www.centos.org/modules/newbb/viewtopic.php?post_id=26959&amp;amp;topic_id=8469"&gt;this
thread&lt;/a&gt;
that says...&lt;/p&gt;
&lt;p&gt;Install dag's repo (&lt;em&gt;&lt;a href="http://dag.wieers.com/rpm/packages/rpmforge-release/"&gt;this
rpm&lt;/a&gt;&lt;/em&gt;), and then
install dkms-ipw3945 (&lt;em&gt;yum will pick up the dependancies&lt;/em&gt;)&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;yum install dkms-ipw3945
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Next enable network manager...&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;chkconfig --level 345 NetworkManager on
chkconfig --level 345 NetworkManagerDispatcher on
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;reboot (seriously) and when you next log in you'll get a little icon in
you system tray where you can manage your WiFi :)&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">nick</dc:creator><pubDate>Thu, 24 May 2007 10:39:00 +0100</pubDate><guid isPermaLink="false">tag:www.linickx.com,2007-05-24:intel-3945abg-wireless-wifi-card-on-centos-5</guid><category>centos</category><category>Enterprise Linux</category><category>Linux</category><category>redhat</category><category>wireless</category></item><item><title>rkhunter rpm for Centos / RedHat</title><link>https://www.linickx.com/rkhunter-rpm-for-centos-redhat</link><description>&lt;p&gt;Whilst doing some routine maintenance, I noticed that I never published
the &lt;a href="https://www.linickx.com/files/rpm/whitebox/4/i386/rkhunter-1.2.9-1.noarch.rpm"&gt;rkhunter rpm I
built&lt;/a&gt;,
the software is &lt;a href="http://www.rootkit.nl/projects/rootkit_hunter.html"&gt;officially supported at
rootkit.nl&lt;/a&gt; but for
ease I wanted a yum available rpm ;)&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">nick</dc:creator><pubDate>Sun, 29 Apr 2007 11:47:00 +0100</pubDate><guid isPermaLink="false">tag:www.linickx.com,2007-04-29:rkhunter-rpm-for-centos-redhat</guid><category>centos</category><category>Enterprise Linux</category><category>Linux</category><category>redhat</category><category>root kit</category><category>rpm</category><category>Security</category></item><item><title>How to Migrate from White Box Linux 4 to CentOS 4.4</title><link>https://www.linickx.com/how-to-migrate-from-white-box-linux-4-to-centos-44</link><description>&lt;p&gt;There are somethings that you just never get round to, my nagios box was
still running whitebox linux, and I've finally gotten round "upgrading"
it to CentOS... yeah ok, upgrade is arguable, but you get my point.&lt;/p&gt;
&lt;p&gt;First off a &lt;strong&gt;warning: Don't do this !&lt;/strong&gt; All the documentation, for
CentOS, RHEL, Fedora, any redhat linux all say, clean installs are the
best way, and upgrades are not advised.... therefore I offer no support
or warranty that this will work, in fact, I you advise you to read this
post, but step away from your consoles !&lt;/p&gt;
&lt;p&gt;But, if you think it might be a laugh, the &lt;a href="http://www.centos.org/modules/smartfaq/faq.php?faqid=19"&gt;centos
documentation&lt;/a&gt;is
a bit old, and not 100% correct, so here is what I did. First up (&lt;em&gt;as
root - obviously&lt;/em&gt;), clear out your yum cache,and install the CentOS gpg
key.&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;yum clean all
rpm --import http://mirror.centos.org/centos/RPM-GPG-KEY-CentOS-4
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Next, install some base centos packages, take not that some need to be
forced on&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;rpm -Uvh --nodeps http://mirror.centos.org/centos/4.4/os/i386/CentOS/RPMS/centos-release-4-4.2.i386.rpm
rpm -ivh http://mirror.centos.org/centos/4.4/os/i386/CentOS/RPMS/python-elementtree-1.2.6-4.2.1.i386.rpm
rpm -ivh http://mirror.centos.org/centos/4.4/os/i386/CentOS/RPMS/python-sqlite-1.1.7-1.2.i386.rpm
rpm -ivh http://mirror.centos.org/centos/4.4/os/i386/CentOS/RPMS/sqlite-3.3.3-1.2.i386.rpm
rpm -Uvh --force http://mirror.centos.org/centos/4.4/os/i386/CentOS/RPMS/python-urlgrabber-2.9.8-2.noarch.rpm
rpm -Uvh --nodeps http://mirror.centos.org/centos/4.4/os/i386/CentOS/RPMS/yum-2.4.3-1.c4.noarch.rpm
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;finally remove the whitebox rpm db.&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;rpm -ev rpmdb-whitebox
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Move any "whitebox" mirrors still in &lt;em&gt;/etc/yum.repos.d&lt;/em&gt; and&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;yum install rpmdb-CentOS
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Once you have that sorted, you can complete the upgrade with&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;yum update
reboot
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;&amp;amp; cross your fingers ;)&lt;br /&gt;
If you come across the following warnings while using yum: Warning,
could not load sqlite, falling back to pickle , I found...&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;yum install python-sqlite
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Fixed the problem. And there we have it, all my boxes are now running
CentOS - yay - just in time to look at the CentOS 5 upgrade ;)&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Dependency Problems ?&lt;/strong&gt;&lt;br /&gt;
If a whitebox rpm is newer than the CentOS one, it won't get upgraded,
this might cause problems when installing new packages via yum. To solve
the problem download the rpm manually from
http://www.centos.org/modules/tinycontent/index.php?id=13 and force an
upgrade&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;rpm --force -Uvh Something-CentOS.rpm
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;&lt;strong&gt;UPDATE:&lt;/strong&gt; If you're using something like &lt;a href="http://www.rootkit.nl/projects/rootkit_hunter.html"&gt;Root Kit
Hunter&lt;/a&gt;, you will
notice a load of md5 hashes fail, these are whitebox rpm's that didn't
need upgrading, to correct the problem you need to replace these with
CentOS versions.. example rkhunter output:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;/sbin/init  [ BAD ]
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Find which rpm, init belongs to&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;# rpm -q --whatprovides /sbin/init
SysVinit-2.85-34.3
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;and upgrade it&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;wget http://www.mirrorservice.org/sites/mirror.centos.org/4.4/os/i386/CentOS/RPMS/SysVinit-2.85-34.3.i386.rpm
rpm --force -Uvh SysVinit-2.85-34.3.i386.rpm
&lt;/code&gt;&lt;/pre&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">nick</dc:creator><pubDate>Tue, 24 Apr 2007 14:16:00 +0100</pubDate><guid isPermaLink="false">tag:www.linickx.com,2007-04-24:how-to-migrate-from-white-box-linux-4-to-centos-44</guid><category>centos</category><category>Enterprise Linux</category><category>Enterprise Linux</category><category>how to</category><category>migrate</category><category>redhat</category><category>upgrade</category><category>wbel</category></item><item><title>How to Migrate from White Box Linux 4 to CentOS 4.4</title><link>https://www.linickx.com/how-to-migrate-from-white-box-linux-4-to-centos-44</link><description>&lt;p&gt;There are somethings that you just never get round to, my nagios box was
still running whitebox linux, and I've finally gotten round "upgrading"
it to CentOS... yeah ok, upgrade is arguable, but you get my point.&lt;/p&gt;
&lt;p&gt;First off a &lt;strong&gt;warning: Don't do this !&lt;/strong&gt; All the documentation, for
CentOS, RHEL, Fedora, any redhat linux all say, clean installs are the
best way, and upgrades are not advised.... therefore I offer no support
or warranty that this will work, in fact, I you advise you to read this
post, but step away from your consoles !&lt;/p&gt;
&lt;p&gt;But, if you think it might be a laugh, the &lt;a href="http://www.centos.org/modules/smartfaq/faq.php?faqid=19"&gt;centos
documentation&lt;/a&gt;is
a bit old, and not 100% correct, so here is what I did. First up (&lt;em&gt;as
root - obviously&lt;/em&gt;), clear out your yum cache,and install the CentOS gpg
key.&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;yum clean all
rpm --import http://mirror.centos.org/centos/RPM-GPG-KEY-CentOS-4
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Next, install some base centos packages, take not that some need to be
forced on&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;rpm -Uvh --nodeps http://mirror.centos.org/centos/4.4/os/i386/CentOS/RPMS/centos-release-4-4.2.i386.rpm
rpm -ivh http://mirror.centos.org/centos/4.4/os/i386/CentOS/RPMS/python-elementtree-1.2.6-4.2.1.i386.rpm
rpm -ivh http://mirror.centos.org/centos/4.4/os/i386/CentOS/RPMS/python-sqlite-1.1.7-1.2.i386.rpm
rpm -ivh http://mirror.centos.org/centos/4.4/os/i386/CentOS/RPMS/sqlite-3.3.3-1.2.i386.rpm
rpm -Uvh --force http://mirror.centos.org/centos/4.4/os/i386/CentOS/RPMS/python-urlgrabber-2.9.8-2.noarch.rpm
rpm -Uvh --nodeps http://mirror.centos.org/centos/4.4/os/i386/CentOS/RPMS/yum-2.4.3-1.c4.noarch.rpm
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;finally remove the whitebox rpm db.&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;rpm -ev rpmdb-whitebox
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Move any "whitebox" mirrors still in &lt;em&gt;/etc/yum.repos.d&lt;/em&gt; and&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;yum install rpmdb-CentOS
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Once you have that sorted, you can complete the upgrade with&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;yum update
reboot
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;&amp;amp; cross your fingers ;)&lt;br /&gt;
If you come across the following warnings while using yum: Warning,
could not load sqlite, falling back to pickle , I found...&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;yum install python-sqlite
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Fixed the problem. And there we have it, all my boxes are now running
CentOS - yay - just in time to look at the CentOS 5 upgrade ;)&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Dependency Problems ?&lt;/strong&gt;&lt;br /&gt;
If a whitebox rpm is newer than the CentOS one, it won't get upgraded,
this might cause problems when installing new packages via yum. To solve
the problem download the rpm manually from
http://www.centos.org/modules/tinycontent/index.php?id=13 and force an
upgrade&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;rpm --force -Uvh Something-CentOS.rpm
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;&lt;strong&gt;UPDATE:&lt;/strong&gt; If you're using something like &lt;a href="http://www.rootkit.nl/projects/rootkit_hunter.html"&gt;Root Kit
Hunter&lt;/a&gt;, you will
notice a load of md5 hashes fail, these are whitebox rpm's that didn't
need upgrading, to correct the problem you need to replace these with
CentOS versions.. example rkhunter output:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;/sbin/init  [ BAD ]
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Find which rpm, init belongs to&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;# rpm -q --whatprovides /sbin/init
SysVinit-2.85-34.3
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;and upgrade it&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;wget http://www.mirrorservice.org/sites/mirror.centos.org/4.4/os/i386/CentOS/RPMS/SysVinit-2.85-34.3.i386.rpm
rpm --force -Uvh SysVinit-2.85-34.3.i386.rpm
&lt;/code&gt;&lt;/pre&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">nick</dc:creator><pubDate>Tue, 24 Apr 2007 14:16:00 +0100</pubDate><guid isPermaLink="false">tag:www.linickx.com,2007-04-24:how-to-migrate-from-white-box-linux-4-to-centos-44</guid><category>centos</category><category>Enterprise Linux</category><category>Enterprise Linux</category><category>how to</category><category>migrate</category><category>redhat</category><category>upgrade</category><category>wbel</category></item><item><title>Tripwire 2.4.1.1 rpm for CentOS, Redhat ( RHEL ) 4</title><link>https://www.linickx.com/tripwire-2411-rpm-for-centos-redhat-rhel-4</link><description>&lt;p&gt;Following &lt;a href="https://www.linickx.com/blog/archives/229/tripwire-rpm-for-rhel-4-wbel-4-centos-4/#comments"&gt;a
request&lt;/a&gt;
I've rebuilt a later tripwire rpm (&lt;em&gt;2.4.1.1&lt;/em&gt;); I think at this point it
would be prudent to point out that the &lt;a href="https://www.linickx.com/files/rpm/"&gt;rpms found
here&lt;/a&gt; are not maintained, and I do
not offer any kind of support - you use them at your own risk - but
you're welcome to make requests !&lt;/p&gt;
&lt;p&gt;&lt;a href="https://www.linickx.com/files/rpm/whitebox/4/i386/tripwire-2.4.1.1-1.i386.rpm"&gt;tripwire-2.4.1.1-1.i386.rpm&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;My Yum repo has also been updated, &lt;a href="https://www.linickx.com/files/rpm/linickx-whitebox.repo"&gt;config file
here&lt;/a&gt; :D&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">nick</dc:creator><pubDate>Tue, 17 Apr 2007 13:28:00 +0100</pubDate><guid isPermaLink="false">tag:www.linickx.com,2007-04-17:tripwire-2411-rpm-for-centos-redhat-rhel-4</guid><category>Blog</category><category>centos</category><category>Enterprise Linux</category><category>Linux</category><category>redhat</category><category>rpm</category><category>Security</category></item><item><title>Service Recovery Scripts &amp; Error Page Tips.</title><link>https://www.linickx.com/service-recovery-scripts-error-page-tips</link><description>&lt;p&gt;A couple of weeks ago, I was proper ill with flu; the problem with
looking after your own server is that only you can fix it - it's well
and good having monitoring systems (&lt;em&gt;nagios&lt;/em&gt;) telling you about faults,
but if you can't read or see the alerts the fault won't get resolved.&lt;/p&gt;
&lt;p&gt;During this time I was ill, for an unknown reason the mySQL process on
my server died, as such my website (&lt;em&gt;and others I look after&lt;/em&gt;) were down
for 8 hours. The fix was simple, one command, restart the service and
normal service was resumed (&lt;em&gt;excuse the pun&lt;/em&gt;).&lt;/p&gt;
&lt;p&gt;This led to me to the conclusion that there must be a way to get the
server to fix it's self. after all, why do a job when you can get a
computer to do it for you ! Fortunately I had a
&lt;abbr title="short moment of genuis"&gt;light bulb moment&lt;/abbr&gt; and
realised that I could use the init scripts that are provided by redhat,
the below code will restart apache (&lt;em&gt;httpd&lt;/em&gt;) and mySQL on a redhat based
system in the event that the service was not stopped cleanly. (&lt;em&gt;In-fact
this config has only be tested on CentOS, your mileage may vary on
anything else&lt;/em&gt;)&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;#!/bin/bash

# taken from redhast default scripts - /etc/rc.d/init.d/functions

# Set up a default search path.
PATH="/sbin:/usr/sbin:/bin:/usr/bin:/usr/X11R6/bin"
export PATH

status() {
        local base=${1##*/}
        local pid

        # Test syntax.
        if [ "$#" = 0 ] ; then
                echo $"Usage: status {program}"
                return 1
        fi

        # First try "pidof"
        pid=`pidof -o $$ -o $PPID -o %PPID -x $1 ||
             pidof -o $$ -o $PPID -o %PPID -x ${base}`
        if [ -n "$pid" ]; then
# Uncomment this if you want OK messages
#               echo $"${base} (pid $pid) is running..."
                return 0
        fi

        # Next try "/var/run/*.pid" files
        if [ -f /var/run/${base}.pid ] ; then
                read pid &amp;lt; /var/run/${base}.pid
                if [ -n "$pid" ]; then
                        echo $"${base} dead but pid file exists"
                        /etc/init.d/${base} restart
                        return 1
                fi
        fi
        # See if /var/lock/subsys/${base} exists
        if [ -f /var/lock/subsys/${base} ]; then
                echo $"${base} dead but subsys locked"
                /etc/init.d/${base} restart
                return 2
        fi
        echo $"${base} is stopped"
        return 3
}

# found in /etc/init.d/httpd
httpd=${HTTPD-/usr/sbin/httpd}

status mysqld
status $httpd
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;If you save this, as &lt;strong&gt;/etc/cron.hourly/auto_recovery.sh&lt;/strong&gt; , then do
&lt;strong&gt;chmod +x /etc/cron.hourly/auto_recovery.sh&lt;/strong&gt; , assuming you've not
changed the default cron setup, every hour mySQL &amp;amp; httpd will be
checked, if they have died the'll be restarted and root will get an
e-mail about what happened.&lt;/p&gt;
&lt;p&gt;Cool eh !&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;A final finishing touch:&lt;/strong&gt; I wanted to change the default "Database
Down" error messages on my two most popular applications.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="http://allforces.com/2006/06/18/custom-wordpress-errors/"&gt;Melvin Rivera has written a tutorial on how to customize the
    wordpress error
    page&lt;/a&gt;,
    note that it involves editing a file outside of wp-content, that
    means you'll have to re-do this "hack" every time you upgrade
    wordpress.&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;PHPBB: Setting a custom error page on that is really easy, first
    create a php page displaying your message. Then at the bottom of
    /path/to/phpbb-install/includes/db.php you'll see&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;// Make the database connection.
$db = new sql_db($dbhost, $dbuser, $dbpasswd, $dbname, false);
if(!$db-&amp;gt;db_connect_id)
{
message_die(CRITICAL_ERROR, "Could not connect to the database");
}
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;change it to&lt;/p&gt;
&lt;pre&gt;&lt;code&gt; // Make the database connection.
$db = new sql_db($dbhost, $dbuser, $dbpasswd, $dbname, false);
if(!$db-&amp;gt;db_connect_id)
{
 include("/path/to/my-custom-error-page.php");
        die();
}
&lt;/code&gt;&lt;/pre&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Now if you database dies, for the time it's down (&lt;em&gt;before cron fixes
it&lt;/em&gt;) wordpress &amp;amp; phpbb sites would get a much prettier error message.
Obviously there's no solution for apache as there's nothing to serve the
pages, but hopefully this kind of thing doesn't happen to often :D&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">nick</dc:creator><pubDate>Tue, 06 Mar 2007 13:32:00 +0000</pubDate><guid isPermaLink="false">tag:www.linickx.com,2007-03-06:service-recovery-scripts-error-page-tips</guid><category>apache</category><category>Enterprise Linux</category><category>Fedora</category><category>httpd</category><category>Linux</category><category>monitoring</category><category>mysql</category><category>recovery</category><category>WordPress</category></item></channel></rss>