From 8e7793c1c34f035f6907004b08da2ba17d06b68b Mon Sep 17 00:00:00 2001 From: Greg Sabino Mullane Date: Wed, 26 Mar 2008 17:48:58 -0400 Subject: [PATCH] POD fixes by Robert Treat. --- check_postgres.pl | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/check_postgres.pl b/check_postgres.pl index 4f2e6ce9c..6de3d8332 100755 --- a/check_postgres.pl +++ b/check_postgres.pl @@ -2563,7 +2563,7 @@ The current supported actions are: =item B (symlink: C) Checks the current number of connections for one or more databases, and optionally comparing it to the maximum -allowed, which is determined the the 'max_connections' setting. The warning and option can take one of three forms. +allowed, which is determined by the 'max_connections' setting. The warning and option can take one of three forms. First, a simple number can be given, which represents the number of connections at which the alert will be given. This choice does not use the max_connections setting. Second, the percentage of available connections can be given. Third, a negative number can be given which represents the number of connections left until max_connections is @@ -2576,9 +2576,6 @@ Example 1: Give a warning when the number of connections on host quirm reaches 1 Example 2: Give a critical when we reach 75% of our max_connections setting on hosts lancre or lancre2. check_postgres_backends --warning='75%' --critical='75%' --host=lancre,lancre2 -Example 2: Give a critical when we reach 75% of our max_connections setting on hosts lancre or lancre2. - check_postgres_backends --warning='75%' --critical='75%' --host=lancre,lancre2 - Example 3: Give a warning when there are only 10 more connection slots left on host plasmid, and a critical when we have only 5 left. check_postgres_backends --warning=-10 --critical=-5 --host=plasmid -- 2.39.5