man pound Command

Man page for apt-get pound Command

Man Page for pound in Linux

Ubuntu Man Command : man pound

Man Pound  Command

This tutorial shows the man page for man pound in linux.

Open terminal with 'su' access and type the command as shown below:
man pound

Result of the Command Execution shown below:

POUND(8)                                                               System Manager's Manual                                                              POUND(8)

pound HTTP/HTTPS reverse proxy and load balancer

pound [ v] [ c] [ V] [ f config_file] [ p pid_file]

Pound is a reverse proxy load balancing server. It accepts requests from HTTP/HTTPS clients and distributes them to one or more Web servers. The HTTPS
requests are decrypted and passed to the back ends as plain HTTP.

If more than one back end server is defined, Pound chooses one of them randomly, based on defined priorities. By default, Pound keeps track of associations
between clients and back end servers (sessions).

In general Pound needs three types of objects defined in order to function: listeners, services and back ends.

A listener is a definition of how Pound receives requests from the clients (browsers). Two types of listeners may be defined: regular HTTP listeners
and HTTPS (HTTP over SSL/TLS) listeners. At the very least a listener must define the address and port to listen on, with additional requirements for
HTTPS listeners.

A service is the definition of how the requests are answered. The services may be defined within a listener or at the top level (global). When a
request is received Pound attempts to match them to each service in turn, starting with the services defined in the listener itself and, if needed,
continuing with the services defined at the global level. The services may define their own conditions as to which requests they can answer: typically
this involves certain URLs (images only, or a certain path) or specific headers (such as the Host header). A service may also define a session mecha Äê
nism: if defined future requests from a given client will always be answered by the same back end.

Back ends
The back ends are the actual servers for the content requested. By itself, Pound supplies no responses all contents must be received from a "real"
web server. The back end defines how the server should be contacted.

Three types of back ends may be defined: a "regular" back end which receives requests and returns responses, a "redirect" back end in which case Pound
will respond with a redirect response, without accessing any back end at all, or an "emergency" back end which will be used only if all other backends
are "dead".

Multiple back ends may be defined within a service, in which case Pound will load balance between the available back ends.

If a back end fails to respond it will be considered "dead", in which case Pound will stop sending requests to it. Dead back ends are periodically
checked for availability, and once they respond again they are "resurected" and requests are sent again their way. If no back ends are available (none
were defined, or all are "dead") then Pound will reply with "503 Service Unavailable", without checking additional services.

The connection between Pound and the back ends is always via HTTP, regardless of the actual protocol used between Pound and the client.

Options available (see also below for configuration file options):

v Verbose mode: error messages will be sent to stdout even if Pound was configured to log to syslog. This applies only to startup messages, before Pound
puts itself in the background. Normal operational messages will still go to syslog.

V Print version: Pound will exit immediately after printing the current version and configuration flags.

c Check only: Pound will exit immediately after parsing the configuration file. This may be used for running a quick syntax check before actually acti Äê
vating a server.

f config_file
Location of the configuration file (see below for a full description of the format). Default: /usr/local/etc/pound.cfg

p pid_file
Location of the pid file. Pound will write its own pid into this file. Normally this is used for shell scripts that control starting and stopping of
the daemon. Default: /var/run/

In general, any number of back end servers may be specified. Use the priority to affect the load distribution among unequal performance servers.

One (or more) copies of Pound should be started at boot time. Use "big iron" if you expect heavy loads: while Pound is as light weight as I know how to make
it, with a lot of simultaneous requests it will use quite a bit of CPU and memory. Multiple CPUs are your friend.

Each line in the file is considered a complete configuration directive. The directives are case insensitive. Empty lines or lines starting in '

Related Topics

Apt Get Commands