Servers Getting Started with Apache 1.3 Page 7

Getting Started with Apache 1.3 Page 7




After you unpack the binary package, there should be a file named
install-bindist.sh in the top-level directory. To install
the Apache package, execute this script with a single parameter: the
location of the ServerRoot you want it to create. For example:

  
    # cd /tmp
    # zcat apache_1.3.12-i386-whatever-linux2.tar.gz | tar xf -
    # cd apache_1.3.12
    # ./install-bindist.sh /usr/local/web/apache
  

This should install the binary and documentation as follows:

Directory tree Location
  1. Apache source tree
Not installed
  1. Apache ServerRoot
/usr/local/web/apache
  1. Apache DocumentRoot
/usr/local/web/apache/htdocs

In other words, with the exception of the source code, the script
will install the Apache elements in the locations mentioned by
the assumptions at the beginning of
this article.

The source directory in the above example is still where you unpacked
it, at /tmp/apache_1.3.12/src/.

Installing on Windows

Installing the prebuilt package on Windows is a snap. Once you’ve
downloaded it into some working directory (such as
C:TEMP), just double-click on the package and away you
go. By default, it will use the directories mentioned in the
assumptions section of this article (that’s
why I assumed those particular locations), but you can change these
during the installation.

Note:
It is generally a very good idea to remove any
existing Apache installation before installing an upgrade. Go to
the ‘Add/Remove Programs’ control-panel to remove any version of
Apache that’s already installed. Your configuration files will
not be touched, so you’ll be able to use them for the new version
after you install it.

Checking the Configuration

By this point you should have an Apache binary application on your
system, just rarin’ to go and start serving files. Before you actually
turn it loose, though, you should make sure you’ve dotted all the eyes
and crossed all the teas.

Verifying the ServerName

For a Windows installation, edit the confhttpd.conf file
under your ServerRoot directory. (Use whatever editor you like, as long
as it creates normal text files as output; Notepad works just fine.)
Look through the file for the word ‘ServerName‘ at the
beginning of a line, and make sure that the second word on that line
is a valid hostname or IP address (such as localhost,
foo.bar.com, or 127.0.0.1). If it isn’t,
Apache won’t start.

For the very best results, you should verify that the ServerName
directive in your httpd.conf file matches your system’s
actual fully-qualified domain name. If your system is named
“www.foo.bar.com”, then that’s what you should put on the
ServerName directive line.

Latest Posts

KVM vs VMware Hypervisor Comparison 2020

The KVM vs VMware hypervisor comparison is a classic debate. Hypervisors have increased in usability and power over the last several years as more...

Compare HP’s iLo & Dell’s iDRAC Server Management Tools

Most servers shipped from the major manufacturers today come with some type of out-of-band management tool or baseboard management controller (BMC). Two of the...

Get-MsolUser PowerShell Attributes & Properties

This article has been updated for 2020. Please note that WAAD was retired in 2018, but the cmdlets listed in this article are still...

Microsoft Azure PowerShell Scripts and Commands

Using PowerShell scripts and commands for quickly executing tasks in Windows operating systems offers a number of benefits over traditional scripting languages, such as...

Microsoft Hyper V Review

Microsoft Hyper-V: The Bottom line Microsoft Hyper-V lagged behind VMware's virtualization tool, one of the most popular tools in the space, when it was first...

Related Stories