Lines Matching full:serve
124 The number of threads to create to serve clients. Use 1 for no threading.
309 larger than serve\-expired\-client\-timeout if that is enabled.
1391 .B serve\-expired: \fI<yes or no>
1392 If enabled, Unbound attempts to serve old responses from cache with a
1393 TTL of \fBserve\-expired\-reply\-ttl\fR in the response without waiting for the
1397 .B serve\-expired\-ttl: \fI<seconds>
1399 disables the limit. This option only applies when \fBserve\-expired\fR is
1403 .B serve\-expired\-ttl\-reset: \fI<yes or no>
1404 Set the TTL of expired records to the \fBserve\-expired\-ttl\fR value after a
1409 .B serve\-expired\-reply\-ttl: \fI<seconds>
1411 \fBserve\-expired\-client\-timeout\fR is also used then it is RECOMMENDED to
1414 .B serve\-expired\-client\-timeout: \fI<msec>
1416 essentially enables the serve-stale behavior as specified in
1422 .B serve\-original\-ttl: \fI<yes or no>
2007 servers for the remaining time. When prefetch is enabled (or serve\-expired),
2063 .B ede\-serve\-expired: \fI<yes or no>
2545 Path to a certificate that we should be able to serve existing connection from
2602 This module does not interact with the \fBserve\-expired*\fR and
2734 This module interacts with the \fBserve\-expired\-*\fR options and will reply
2792 .B cachedb-check-when-serve-expired: \fI<yes or no>\fR
2794 When \fBserve\-expired\fR is enabled, without \fBserve\-expired\-client\-timeout\fR, it then
2797 cachedb also has no valid contents, the serve expired response is sent.
2798 If also \fBserve\-expired\-client\-timeout\fR is enabled, the expired response
2845 Unbound is configured with \fBserve-expired\fR and \fBserve-expired-ttl\fR is 0,