Outsource Hosting Support

Login as root using SSH and type the following commands:

# cd /scripts
# ./updatenow
# ./easyapache

Once this is done, you will get a menu on your screen which will ask you to select the options with which you need to build apache. Kindly select the appropriate option as per your requirements and proceed at the end it will restart apache and you will be able to use the features that you have selected.

This article has been published by Outsource Hosting Support, technical support service providers for web hosting companies, Internet service providers, Data Centers and Software companies. Visit us at www.OutsourceHostingSupport.com

Popularity: 71% [?]

Apache web server has a flexible mechanism for accepting requests and dispatching children to process them which are abstracted in to Multi Processing Modules (MPM). The MPM used by default in Red Hat Enterprise Linux is prefork, which spawns multiple child process when needed just like Apache 1.3. Other MPMs are not yet available; through directives for some appear in the configuration file.

Dynamic module loading allows a dedicated web server administrator to change the behavior of Apache webserver. This can be done without recompiling any source code, and simply specifying the use of a given module. A commonly used module is mod_per1, which is used to increase Perl CGI script execution speed.

More information about Apache HTTP Server is on their website is http://http.apache.org

Service Profile for Apache web server: HTTPD
1. Type: SystemV-managed service
2. Packages:httpd, httpd-devel, httpd-manual
3. Daemon:/usr/sbin/httpd
4. Scripts: /etc/init.d/httpd
5. Ports: 80(http), 43(https)
6. Configuration: /etc/http/*, /var/www/*
7. Related: system-config-httpd, mod_ssl

Apache web server is an SELinux restricted service when enforcing the default targeted policy on a Red Hat Enterprise Linux, version 4 system. The server uses a number of SELinux contexts for its files.

This article has been published by Outsource Hosting Support, technical support service providers for web hosting companies, Internet service providers, Data Centers and Software companies. Visit us at www.OutsourceHostingSupport.com

Popularity: 64% [?]

Mail User Agent

1. Mail user agent (MUA) passes message to mail transport agent(MTA)
2. MTA routes messages to destination, giving to other intermediate MTAs as necessary
3. Domain MTA passes message to mail delivery agent (MDA)
4. User receives message

The mail delivery process begins when the user decides to send a composed message. The user’s mail agent passes the message along to its configured MTA, usually a central mail gateway. With Sendmail, the user program calls sendmail as a non-privileged mail submission program (MSP) which will relay it to the MTA, This gateway reads the message and extracts the destination address from it. The MTA will unravel each mail address, gathering networks, machines, and users to whom to send the message.

Once the MTA has verified all destination email addresses, it will notify the MUA that the mail was sent. Next, the MTA will deliver the message to the configured mail exchanger (MX) for each domain; should the primary one be down, the next MX for the domain will be chosen. If no mail exchangers are available (e.g. they’re all down), then the MTA will queue the message and attempt deliver later.

When the message reaches the final destination, the target MTA hands the message to the system MDA. Under many systems, the MTA and the MDA are the same program, sendmail. The MDA will store the message in a spool file, or pass it through filters, or any perform whatever other instructions it is given for the particular site. User may then retrieve their mail either locally by reading from a spool file, remotely, by using a protocol such as POP or IMAP.

This article has been published by Outsource Hosting Support, technical support service providers for web hosting companies, Internet service providers, Data Centers and Software companies. Visit us at www.OutsourceHostingSupport.com

Popularity: 35% [?]

Network file service (NFS)

1. The Red Hat Enterprise Linux NFS service is similar to other BSD and UNIX variants
2. Exports are listed in /etc/exports
3. Server notified of changes to export list with exportfs –r or services nfs reload
4. Shared directories are accessed through the mount command
5. The NFS server is an RPC service and thus requires portmap

NFS server software includes with Red Hat Enterprise Linux is composed of three facilities, included in the portmap and nfs-utils rpms:

Portmap: maps calls made from other machines to the correct RPC service
nfs (in kernel): translates NFS requests into requests on the local file system
rpc.mountd: mounts and unmounts file systems

These all run as daemons and are started at boot time from the portmap and nfs System V initialization scripts in the usual way. The file systems to share are listed in /etc/exports.

This article has been published by Outsource Hosting Support, technical support service providers for web hosting companies, Internet service providers, Data Centers and Software companies. Visit us at www.OutsourceHostingSupport.com

Popularity: 34% [?]

The caching name server configuration forwards queries and caches results.

1. Caching-nameserver RPM package provides a working named.conf BIND configuration.
2. Also provides internet root server ‘hints’ or references via named.ca
3. /etc/resolve.conf should include nameserver 127.0.0.1

The caching-nameserver package doesn’t serve as an authoritative server for any domain. Its job is to fulfill client requests, and to the cache the retrieved information for subsequent lookups. It must be installed with the BIN packages. The name server entry in /etc/resolve.conf should then be set to 127.0.0.1.

The caching-nameserver package does not contain any binary files. It simply applies a standard configuration to BIND. It is recommended that a forwarders entry be added to the options sections of named.conf. This will provide better performance, and reduce the usage of shared network resources. The caching-nameserver configuration can be a good starting point for configuration name servers which are not caching-only.

This article has been published by Outsource Hosting Support, technical support service providers for web hosting companies, Internet service providers, Data Centers and Software companies. Visit us at www.OutsourceHostingSupport.com

Popularity: 34% [?]

If you select the DNS Server package group, either during initial installation or from the system-config-packages GUI, the bind-chroot package will be installed. This package contains a tree of file which can be used as a chroot jail for the named program from the bind package.

When the bind-chroot package is installed, named runs in a chroot environment. This environment is defined in the /etc/sysconfig/named file by a variable called ROOTDIR: ROOTDIR=/var/named/chroot .

When this variable is set the named process is chrooted to the directory specified in the variables prior to reading any configuration files. The default chroot directory is /var/named/chroot/. This means that all of bin’s configuration files will be stored relative to this directory. So, for example, the main configuration file, named.conf, will be in /var/named/chroot/etc/named.conf instead of /etc/named.conf. All other configuration and zone files will also be relative to this directory.

If you remove the ROOTDIR setting then named runs without chrooting first, so all files and directories are related to the root (/) directory. The /etc/sysconfig/named file can also set options passed to the named command.

This article has been published by Outsource Hosting Support, technical support service providers for web hosting companies, Internet service providers, Data Centers and Software companies. Visit us at www.OutsourceHostingSupport.com

Popularity: 36% [?]