From: Marcin Siodelski Date: Mon, 16 Jan 2023 21:25:08 +0000 (+0100) Subject: [#2688] Mention that tcp-user-timeout is in seconds X-Git-Tag: Kea-2.2.1~30 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=a1c3c74cbc87da08b1d77fab6509394b3a08f6d6;p=thirdparty%2Fkea.git [#2688] Mention that tcp-user-timeout is in seconds --- diff --git a/doc/sphinx/arm/dhcp4-srv.rst b/doc/sphinx/arm/dhcp4-srv.rst index f75ee6e3fd..96e106b039 100644 --- a/doc/sphinx/arm/dhcp4-srv.rst +++ b/doc/sphinx/arm/dhcp4-srv.rst @@ -579,8 +579,8 @@ read and write operations. Moreover, the ``read-timeout`` and ``write-timeout`` parameters can only be specified for the MySQL backend. Setting them for any other backend type causes a configuration error. -To set a timeout for PostgreSQL, use the ``tcp-user-timeout`` parameter -instead. For example: +Use the ``tcp-user-timeout`` parameter to set a timeout for PostgreSQL +in seconds. For example: :: diff --git a/doc/sphinx/arm/dhcp6-srv.rst b/doc/sphinx/arm/dhcp6-srv.rst index 2fed23c104..d5e86aec0a 100644 --- a/doc/sphinx/arm/dhcp6-srv.rst +++ b/doc/sphinx/arm/dhcp6-srv.rst @@ -536,8 +536,8 @@ read and write operations. Moreover, the ``read-timeout`` and ``write-timeout`` parameters can only be specified for the MySQL backend. Setting them for any other backend type causes a configuration error. -To set a timeout for PostgreSQL, use the ``tcp-user-timeout`` parameter -instead. For example: +Use the ``tcp-user-timeout`` parameter to set a timeout for PostgreSQL +in seconds. For example: ::