Status codes are issued by a server in response to a client's request made to the server. It includes codes from IETF Request for Comments (RFCs), other specifications, and some additional codes used in some common applications of the HTTP. The first digit of the status code specifies one of five standard classes of responses. The Status module allows a server administrator to find out how well their server is performing. A HTML page is presented that gives the current server statistics in an easily human readable form. If required this page can be made to automatically refresh in certain duration. When running as proxy httpd may be configured to do caching of documents resulting in faster response times. Authors Ari Luotonen, Henrik Frystyk Nielsen, Tim Berners-Lee Status Version 3.0A is the final version. It was generated July 15 1996.
httpd is the Apache HyperText Transfer Protocol (HTTP) server program. It is designed to be run as a standalone daemon process. When used like this it will create a pool of child processes or threads to handle requests.
In general, httpd should not be invoked directly, but rather should be invoked via apachectl on Unix-based systems. The httpd RPM package provides the /usr/sbin/httpd daemon and its configuration files.
Service Control
To manage the httpd service on demand, use the service tool or run the /etc/init.d/httpd script directly:
The available commands are:
| Command | Description |
|---|---|
| start | Start the httpd daemon. |
| stop | Stop the httpd daemon. |
| restart | Equivalent to a stop and then a start command sequence. |
| condrestart | If the httpd daemon is currently running, this is the same as a restart command. If the daemon is not running, no action is taken. Often used in RPM package installation to avoid starting a service not already running. |
| reload | Force the httpd daemon to re-read its configuration files without a service interruption. |
| status | If the httpd daemon is running, report its PID (Process ID). If not running, report that, too. |
| fullstatus | Displays a full status report from mod_status. For this to work, you need to have mod_status enabled on your server and a text-based browser such as lynx available on your system. The URL used to access the status report can be set by editing the STATUSURL variable in the script. |
| graceful | Gracefully restarts the Apache httpd daemon. If the daemon is not running, it is started. This differs from a normal restart in that currently open connections are not aborted. A side effect is that old log files will not be closed immediately. This means that if used in a log rotation script, a substantial delay may be necessary to ensure that the old log files are closed before processing them. This command automatically checks the configuration files as in configtest before initiating the restart to make sure Apache doesnât die. This is equivalent to apachectl -k graceful. |
| help | Show the usage of command /usr/sbin/httpd. |
| configtest | Run a configuration file syntax test. It parses the configuration files and either reports Syntax Ok or detailed information about the particular syntax error. This is equivalent to apachectl -t. |
Configuration
To manage the httpd service at boot time, use chkconfig tool:
Behavior of the httpd service can be tailored using the /etc/httpd/conf/httpd.conf file. A default version of this file is shown below:
httpd is the Apache HyperText Transfer Protocol (HTTP) server program. It is designed to be run as a standalone daemon process. When used like this it will create a pool of child processes or threads to handle requests.
In general, httpd should not be invoked directly, but rather should be invoked via apachectl on Unix-based systems. The httpd RPM package provides the /usr/sbin/httpd daemon and its configuration files.
Service Control
To manage the httpd service on demand, use the service tool or run the /etc/init.d/httpd script directly:
The available commands are:
| Command | Description |
|---|---|
| start | Start the httpd daemon. |
| stop | Stop the httpd daemon. |
| restart | Equivalent to a stop and then a start command sequence. |
| condrestart | If the httpd daemon is currently running, this is the same as a restart command. If the daemon is not running, no action is taken. Often used in RPM package installation to avoid starting a service not already running. |
| reload | Force the httpd daemon to re-read its configuration files without a service interruption. |
| status | If the httpd daemon is running, report its PID (Process ID). If not running, report that, too. |
| fullstatus | Displays a full status report from mod_status. For this to work, you need to have mod_status enabled on your server and a text-based browser such as lynx available on your system. The URL used to access the status report can be set by editing the STATUSURL variable in the script. |
| graceful | Gracefully restarts the Apache httpd daemon. If the daemon is not running, it is started. This differs from a normal restart in that currently open connections are not aborted. A side effect is that old log files will not be closed immediately. This means that if used in a log rotation script, a substantial delay may be necessary to ensure that the old log files are closed before processing them. This command automatically checks the configuration files as in configtest before initiating the restart to make sure Apache doesnât die. This is equivalent to apachectl -k graceful. |
| help | Show the usage of command /usr/sbin/httpd. |
| configtest | Run a configuration file syntax test. It parses the configuration files and either reports Syntax Ok or detailed information about the particular syntax error. This is equivalent to apachectl -t. |
Apache Mod Status
Configuration
To manage the httpd service at boot time, use chkconfig tool:
Status.tivo.com
Behavior of the httpd service can be tailored using the /etc/httpd/conf/httpd.conf file. A default version of this file is shown below: