Fix alphabetical order of uuid
>From bb84a45b848b879f41ab37343b50057323a6ff19 Mon Sep 17 00:00:00 2001 From: Alexandar Lazic <[email protected]> Date: Tue, 1 Jun 2021 00:27:01 +0200 Subject: [PATCH] DOC/MINOR: move uuid in the configuration to the right alphabetical order
This patch can be backported up to 2.1 where the uuid fetch was introduced --- doc/configuration.txt | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/doc/configuration.txt b/doc/configuration.txt index 11c38945c..9264f03ce 100644 --- a/doc/configuration.txt +++ b/doc/configuration.txt @@ -17433,11 +17433,6 @@ rand([<range>]) : integer needed to take some routing decisions for example, or just for debugging purposes. This random must not be used for security purposes. -uuid([<version>]) : string - Returns a UUID following the RFC4122 standard. If the version is not - specified, a UUID version 4 (fully random) is returned. - Currently, only version 4 is supported. - srv_conn([<backend>/]<server>) : integer Returns an integer value corresponding to the number of currently established connections on the designated server, possibly including the connection being @@ -17528,6 +17523,11 @@ thread : integer the function, between 0 and (global.nbthread-1). This is useful for logging and debugging purposes. +uuid([<version>]) : string + Returns a UUID following the RFC4122 standard. If the version is not + specified, a UUID version 4 (fully random) is returned. + Currently, only version 4 is supported. + var(<var-name>) : undefined Returns a variable with the stored type. If the variable is not set, the sample fetch fails. The name of the variable starts with an indication -- 2.25.1
