Prev: Next: , Up: Configuration[Contents][Index]


9.8 Timeouts

Directives discussed in this section set various timeout values. Their argument is an integer expressing the value in seconds.

Global directive: Alive n

Specify how often should pound check for the status of backend servers marked as dead (i.e. inaccessible). It is a good idea to set this as low as possible – it will find resurrected hosts faster. However, if you set it too low it will consume resources.

Default is 30 seconds.

Global directive: Client n

Specify for how long pound will wait for a client request (default: 10 seconds). It will drop the connection if client doesn’t send any data within this interval.

This value can be overridden for specific listeners.

Global directive: TimeOut n

Specify for how long pound will wait for the backend to respond (default: 15 seconds).

This value can be overridden for specific backends.

Global directive: ConnTO n

Specify for how long pound will wait for a connection to a backend to be established. Default is the same as the TimeOut value.

This value can be overridden for specific backends.

Global directive: WSTimeOut n

Specify for how long pound will wait for data from either backend or client in a connection upgraded to WebSocket protocol. Default is 600 seconds.

This value can be overridden for specific backends.

Global directive: Grace n

How long should pound continue to answer existing connections after a receiving a ‘INT’ or ‘HUP’ signal (default: 30 seconds). The configured listeners are closed immediately. You can bypass this behaviour by stopping pound with a ‘TERM’ or ‘QUIT’ signal, in which case the program exits without any delay.


Prev: Next: , Up: Configuration[Contents][Index]