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

  • Descarga
  • Añadir a mis manuales
  • Imprimir
  • Pagina
    / 96
  • Tabla de contenidos
  • MARCADORES
  • Valorado. / 5. Basado en revisión del cliente
Vista de pagina 18
Chapter 3. Getting started
Clean slate:
We will start by removing the existing configuration script. This may seem dramatic
but this course seeks to explain every single line of the configuration file that will
finally be written. After we delete the file we will note that the web server won’t
start.
Simplest configuration:
The aim of this section is to give us enough configuration so that the server will at
least start, even if it won’t do anything useful.
Two more lines
We will add two more lines to the most basic configuration file we can have. The
first will just help the configuration file make more sense and the second will turn off
many defaults so we can see them explicitly when we need them.
Deleting the configuration file is easy. Go on, you know you’ve always wanted to do
it! What’s the worst that could happen?
# rm /etc/httpd/conf/httpd.conf
rm: remove regular file ‘/etc/httpd/conf/httpd.conf’? y
Figure 3-1. Deleting the configuration file
The web server will not start now. First it will complain about not having a configu-
ration file.
# /etc/init.d/httpd start
Starting httpd: grep: /etc/httpd/conf/httpd.conf: No such file or directory
httpd: could not open document config file /etc/httpd/conf/httpd.conf
[FAILED]
Figure 3-2. Failing to start the server with no configuration
Close observers will notice that it complains twice. The first is an error from the grep
command. This is just a Red Hat Linux feature that we can ignore. (The Red Hat
Linux start script checks to make sure that you aren’t using an Apache 1 configuration
file.) The second error message comes from httpd and is the one we are interested in.
Next, we will create an empty configuration file and see that that just changes the
error message.
# touch /etc/httpd/conf/httpd.conf
# /etc/init.d/httpd start
Starting httpd: no listening sockets available, shutting down
[FAILED]
Figure 3-3. Failing to start the server with an empty configuration
It must be admitted that as error messages go, “no listening sockets available, shut-
ting down” is a fairly obscure way of saying “you’ve not told me what to do”. Actu-
ally it means, “you’ve not told me to listen for any incoming requests so I might as
well quit now”.
15
Vista de pagina 18
1 2 ... 14 15 16 17 18 19 20 21 22 23 24 ... 95 96

Comentarios a estos manuales

Sin comentarios