最近在公司添加流量监控系统，cati自然是首选。
不过，公司有规定公司IT必须使用redhat as4，由于长时间使用centos，养成了一点点地懒惰…所以，我直接把yum给安装到redhat as4里面去了：P
然后就是按照下面的文章，添加一个源，哈哈，想不到早有人帮我编译好了。哎，大家是不知道，rrdtool在as4下安装需要升级多少pack……
以下是摘录，yum源含内：
RRD & RRDtools Installation
CentOS Debian
CentOS Steps
This How-to assumes the server is being built to a standard configuration using Webmin as a primary management interface. In all cases RPMs are used. If you do not use Webmin skips the steps covering navigation within Webmin.
Dag Wieer’s RPM Repository
The best source for RPMs not part of the CentOS RPM repository is Dag Wieers’ RPM repository system. He has a great how-to on his web-site that was used to build this section. Have a look at it.
1. Import the GPG key for Dag’s site. This helps limit the possibility of installing RPM’s from Dag’s site that are not official.
* Open Webmin console in browser
* Select Other Tab
* Select Command Shell
In the execute command box type:
2. Create a link to Dag’s repository for Yum. Dag might update applications ahead of Red Hat, which drives the CentOS update cycle. So use includepkgs to limit Dag’s repository to applications you specifically want it used for.
* Select Other Tab
* Select the File Manager
Note: Java must installed on your desktop for this to function, and you will likely have to accept the Certificate for your server.
* Navigate to:
/etc/yum.repos.d/
* Create a new file called: dag.repo
* Enter the text below in the new file & save
[dag]
name=Dag RPM Repository for Red Hat Enterprise Linux
baseurl=http://apt.sw.be/redhat/el$releasever/en/$basearch/dag
gpgcheck=1
enabled=1
includepkgs=rrdtool perl-rrdtool
3. Install the RRDtools rpm.
* Select Services Tab
* Select Software Packages
* At the bottom, select the Upgrade Button
With Yum this is a serious limitation of Webmin. There is no way to simply update the Yum directory. The issue goes away if APT is used with Webmin, and is a limitation of Webmin. Switching to Apt is beyond the scope of this how-to.
* Enter perl-rrdtool into the ‘Package from Yum’ box. This will automatically install rrdtool, which perl-rrd-tool is dependent upon.
Rperl-rrdtool installation screenshot
The ‘from ftp or http’ box above enables installation directly from Dag’s repository. Following that path is quick and easy, but does not enable automatic notification of updates.
Debian Steps
This How-to assumes the server is being built to a standard configuration using Webmin as a primary management interface. In all cases .deb files from official repositories are used. If you do not use Webmin skips the steps covering navigation within Webmin.
Debian & Keeping Current
One difficulty with Debian is the past tendency of stable to slowly drift out of step with current application versions. The scope of the organizational, procedural and policy issues that lead to the drift are beyond the scope of this Cookbook How-to and represent the greatest threat to Debian’s longevity.
At time of Writing (August 2005) the Debian RRDtool package in ’stable’ and ‘testing’ are at version 1.0.49-1, and ‘unstable’ at 1.2.11-0.2. RRD released 1.2. in April 2005. If you need features of RRDtools 1.2 you will need to install RRDtool from ‘unstable’ or ‘testing’. While Debian ‘unstable’ & ‘testing’ are very stable operating systems you need to understand both are subject to significant change and that security updates are not managed by Debian’s security team.
You will increase your TCO operating Debian ‘unstable’ and ‘testing’ in a production environment.
Installation for Debian
Installation in Debian is easy with the package included in the main repository.
* Open Webmin
* Select Services Tab
* Select Software Packages
* At the bottom, select the Update Button
This step is is only necessary if you have not updated your system recently.
* Debian maintains two key RRDtool packages, rrdtool and librrds-perl. In most cases you will need librrds-perl to support other applications that use RRDtool.
* Enter librrds-perl into the ‘Package from Apt’ box. This will automatically install any other packages that are required.
For questions, comments or a discussion of our choices please use the contact button below.
