From 70a6a535a23876b8cf2bec75d231e8a4d9d9ad48 Mon Sep 17 00:00:00 2001 From: Greg Sabino Mullane Date: Sat, 17 May 2008 12:08:52 -0400 Subject: [PATCH] Version 1.6.1 docs. --- check_postgres.pl.html | 31 ++++++++++++++++++++----------- 1 file changed, 20 insertions(+), 11 deletions(-) diff --git a/check_postgres.pl.html b/check_postgres.pl.html index 945bea590..b8fc9ece9 100644 --- a/check_postgres.pl.html +++ b/check_postgres.pl.html @@ -49,14 +49,14 @@

VERSION

-

This documents describes check_postgres.pl version 1.6.0

+

This documents describes check_postgres.pl version 1.6.1

SYNOPSIS

   ## Create all symlinks
-  check_postgres.pl --action=build_symlinks
+ check_postgres.pl --symlinks 
   ## Check connection to Postgres database 'pluto':
   check_postgres.pl --action=connection --db=pluto
@@ -257,11 +257,11 @@ inside of it. For example, to run the action "timesync", you may eithe 
   check_postgres_timesync

All the symlinks are created for you in the current directory -if use the action "build_symlinks":

+if use the option --symlinks

-  perl check_postgres.pl --action="build_symlinks"
+ perl check_postgres.pl --symlinks

If the file name already exists, it will not be overwritten. If the file exists -and is a symlink, you can force it to overwrite by using "build_symlinks_force"

+and is a symlink, you can force it to overwrite by using "--action=build_symlinks_force"

Most actions take a --warning and an --critical option, indicating at what point we change from OK to WARNING, and what point we go to CRITICAL. Note that because criticals are always checked first, setting the warning equal to the @@ -373,11 +373,13 @@ Takes no --warning or --critical options.

Runs a custom query of your choosing, and parses the results. The query itself is passed in through the custom_query argument, and should be kept as simple as possible. If at all possible, wrap it in -a view of function to keep things easier to manage. The query should return exactly two columns: the first -is the result that will be checked, and the second is any performance data you want sent. At least one -of warning or critical must be set. What they are set to depends on the type of query you are running. -There are four types of custom_queries that can be run, specified by the checktype argument. If none -is specified, this action defaults to 'integer'. The four types are:

+a view or a function to keep things easier to manage. The query should return one or two columns: the first +is the result that will be checked, and the second is any performance data you want sent.

+
+
+

At least one warning or critical argument must be specified. What these are set to depends on the type of +query you are running. There are four types of custom_queries that can be run, specified by the checktype +argument. If none is specified, this action defaults to 'integer'. The four types are:

integer: @@ -815,7 +817,8 @@ If no units are given, the unit are assumed to be seconds.

but simply creates symlinks in the current directory for each action, in the form check_postgres_<action_name>. If the file already exists, it will not be overwritten. If the action is rebuild_symlinks_force, -then symlinks will be overwritten.

+then symlinks will be overwritten. The option --symlinks is a shorter way of saying +--action=rebuild_symlinks

settings_checksum (symlink: check_postgres_settings_checksum) @@ -1071,6 +1074,12 @@ is needed by the check_disk_space action.

Version 1.6.0 (May 11, 2008) +
+

Add --symlinks option as a shortcut to --action=rebuild_symlinks

+
+ +
Version 1.6.0 (May 11, 2008) +

Add the custom_query action.

-- 2.30.2