Red Hat DIRECTORY SERVER 2.0 - GATEWAY Manual de usuario Pagina 9

  • Descarga
  • Añadir a mis manuales
  • Imprimir
  • Pagina
    / 96
  • Tabla de contenidos
  • MARCADORES
  • Valorado. / 5. Basado en revisión del cliente
Vista de pagina 8
Chapter 1. Installing the software
Changes made to the system
We should quickly examine what changes have been made to the system by the in-
stallation of these packages. The httpd package has obviously installed a web server
(in /usr/sbin/httpd) but it has also installed files in a few other locations.
conf
conf.d
logs
modules
run
magic
README
/var/logs/httpd
/usr/lib/httpd/modules
/var/run
httpd.conf
mod_*.so
*.pid
empty/etc/httpd
Figure 1-8. Configuration hierarchy
The /etc/httpd directory contains all the configuration for the web server and is
where the server looks for everything except the web pages themselves. The conf
subdirectory is for the main configuration file, httpd.conf. The conf.d directory is
for extra elements of configuration which can be automatically included in the server
configuration.
Because this directory is where the server looks for most things there are some sym-
bolic links leaving this directory and pointing to where the system expects such things
to go.
The logs symbolic link points into the /var/logs directory where Red Hat Linux
stores its logs. An httpd subdirectory is used because there will typically be more
than one log file in use at any time. This subdirectory holds them together. We will
discuss log files in detail in Chapter 7.
The modules symbolic link points into /usr/lib where Red Hat Linux keeps its li-
braries. Again, an httpd subdirectory is used to keep all the Apache libraries to-
gether. The libraries are called “modules” under Apache and much of the course will
be devoted to what they can do and how to get them to do it.
The run symbolic link points to /var/run. This directory on a Red Hat Linux system
is used by long-running processes to declare that they are running and to indicate
how to contact them. In practice this means that it is full of PID files. These are files,
named after the process they refer to, containing the process ID (PID) of the process.
For Apache, the PID file is called httpd.pid. In practice, we will not need to know
about this file except to understand how the Apache shutdown procedure works in
Chapter 3.
5
Vista de pagina 8
1 2 3 4 5 6 7 8 9 10 11 12 13 14 ... 95 96

Comentarios a estos manuales

Sin comentarios