Red Hat LINUX 7.2 - OFFICIAL LINUX CUSTOMIZATION GUIDE Guida di Installazione Pagina 179

  • Scaricare
  • Aggiungi ai miei manuali
  • Stampa
  • Pagina
    / 282
  • Indice
  • SEGNALIBRI
  • Valutato. / 5. Basato su recensioni clienti
Vedere la pagina 178
Chapter 15. Apache 179
15.2. Starting and Stopping httpd
During the installation process, a Bourne shell script named httpd was saved in
/etc/rc.d/init.d/. To manually stop, start, or check the status of your server, run httpd with
either stop, start, or status as an argument.
To start your server, type the command:
/sbin/service httpd start
If you are running Apache as a secure server, you will be prompted to fill in your password. After you
type it in, your server will start.
To stop your server, type the command:
/sbin/service httpd stop
The command restart is a shorthand way of stopping and then starting your server. The restart
command explicitly stops and then starts your server. You will be prompted for your password if you
are running Apache as a secure server. The restart command looks like the following:
/sbin/service httpd restart
If you just finished editing something in your httpd.conf file, you do not need to explicitly stop
and start your server. Instead, you can use the reload command. When you use reload, you will
not need to type in your password. Your password will remain cached across reloads, but it will not
be cached between stops and starts. The reload command looks like the following:
/sbin/service httpd reload
By default, the httpd process will start automatically when your machine boots. If you are running
Apache as a secure server, you will be prompted for the secure server’s password after the machine
boots, unless you generated a key for your secure server without password protection.
15.3. Configuration Directives in httpd.conf
The Apache Web server configuration file is /etc/httpd/conf/httpd.conf. The httpd.conf
file is well-commented and somewhat self-explanatory. Its default configuration will work for most
people, so you should not need to change the directives in httpd.conf. However, you may want to
be familiar with the most important configuration options.
The empty srm.conf and access.conf files are also in the /etc/httpd/conf/ directory. The
srm.conf and access.conf files were formerly used, along with httpd.conf, as configuration
files for Apache.
If you need to configure Apache, edit httpd.conf and then either reload, or stop and start the httpd
process. How to reload, stop and start Apache is covered in Section 15.2.
Before you edit httpd.conf, you should first copy the original file to something like httpd.conf-
old, for example. By creating a backup, you can recover potential mistakes made while editing the
new configuration file.
If you do make a mistake, and your Web server does not work correctly, first review what you have
recently edited in httpd.conf. Make sure that you did not make a typo. The next place to look
is your Web server’s error log (/var/log/httpd/error_log). The error log may not be easy to
interpret, depending on your level of experience. If you have just experienced a problem, however, the
last entries in the error log should provide information about what has happened.
The next sections provide short descriptions of the directives included in httpd.conf. These de-
scriptions are not exhaustive. If you need more information, refer to the Apache documentation
Vedere la pagina 178
1 2 ... 174 175 176 177 178 179 180 181 182 183 184 ... 281 282

Commenti su questo manuale

Nessun commento