Results > Posts Filed Under > Server

yum-priorities on CentOS-5 and yum-plugin-priorities on CentOS-4, adding new repositories

Setting up Yum-priorities on CentOS-5 and yum-plugin-priorities on CentOS-4
1. CentOS 5
You should make sure that you have Priorities installed.
1.1. Priorities
yum-priorities is available in the CentOS 5 repositories:
yum install yum-priorities
Plugins are enabled in CentOS 5 by default.
Make sure that yum-priorities is enabled by editing the /etc/yum/pluginconf.d/priorities.conf file, and ensuring that it contains the following lines:
[main]
enabled=1
Edit the .repo files in /etc/yum.repos.d/ and set up priorities by adding the line:
priority=N
to a repository entry, where N is an integer number from 1 to 99.
The …

Install Awstats

Install it with yum (needs rpmforge repo -> http://geekzine.org/2009/01/26/how-to-add-rpmforge-repository-to-centos-52/):
yum install awstats
Now you need to configure the apache permissions:
vi /etc/httpd/conf.d/awstats.conf
You can configure your allow from like this:
allow from 192.168.
Save the file
Then, reload apache config:
/etc/init.d/httpd reload
You need to create a default config for awstats
cd /etc/awstats
cp awstats.model.conf awstats.conf
You can edit the HostAliases Line to put your server name.
HostAliases=”localhost 127.0.0.1″
also, edit the line SiteDomain to full machine name:
SiteDomain=”webserver.example.com”
The  default configuration is now done!
Now you can access your stats on:
http://IpofTheMachine/awstats/awstats.pl

Fix for configure: error: C++ preprocessor “/lib/cpp” fails sanity check & configure: error: *** termcap support not found

configure:5416: result: /lib/cpp
configure:5441: /lib/cpp conftest.cc
cpp: installation problem, cannot exec `cc1plus’: No such file or directory
configure:5441: /lib/cpp conftest.cc
cpp: installation problem, cannot exec `cc1plus’: No such file or directory
configure: error: C++ preprocessor “/lib/cpp” fails sanity check
install the following package
yum install gcc gcc-cpp gcc-c++
=====================================
checking for usb_init in -lusb… no
checking for vorbis_info_init in -lvorbis… no
checking for vpb_open in -lvpb… no
checking for compress in -lz… no
checking for ZT_DIAL_OP_CANCEL in zaptel/zaptel.h… yes
checking for ZT_EVENT_REMOVED in zaptel/zaptel.h… yes
checking for ZT_TCOP_ALLOCATE in zaptel/zaptel.h… yes
configure: error: …

Booting single user mode-rescue mode- Emergency mode. completely explained.

1) Linux Resuce mode.
Using rescue mode, you can access the files stored on your system’s hard drive, even if you cannot actually run Red Hat Linux from that hard drive.
To boot into rescue mode, you must be able to boot the system using one of the following methods:
*
By booting the system from an installation boot diskette made from the bootdisk.img image. [1]
*
By booting the system from an installation boot CD-ROM. [2]
*
By booting the system from the Red Hat Linux CD-ROM …

 Page 3 of 14 « 1  2  3  4  5 » ...  Last »