[check_postgres] [commit] Final docs and sig for 2.0.0
check_postgres at bucardo.org
check_postgres at bucardo.org
Tue Jul 15 21:21:12 UTC 2008
Committed by Greg Sabino Mullane <greg at endpoint.com>
Final docs and sig for 2.0.0
---
check_postgres.pl.asc | 6 +-
check_postgres.pl.html | 124 +++++++++++++++++++++++++----------------------
2 files changed, 69 insertions(+), 61 deletions(-)
diff --git a/check_postgres.pl.asc b/check_postgres.pl.asc
index 570f4ed..42cfae8 100644
--- a/check_postgres.pl.asc
+++ b/check_postgres.pl.asc
@@ -1,6 +1,6 @@
-----BEGIN PGP SIGNATURE-----
-iEYEABEDAAYFAkhhW4gACgkQvJuQZxSWSsg2lQCg6BOVdTxuae16xZ6Fp2RffRv/
-9lkAnRmKDiiDwyBo3bad2Kw/KbscNcPj
-=iIQQ
+iEYEABEDAAYFAkh9EDAACgkQvJuQZxSWSsiQoACgjS0KEoIINtCZ9TAxdyp4jc+g
+yxcAoLW7PwpOv2EglLWRPb13XsS264Yb
+=sHX4
-----END PGP SIGNATURE-----
diff --git a/check_postgres.pl.html b/check_postgres.pl.html
index 1afe32d..87306c6 100644
--- a/check_postgres.pl.html
+++ b/check_postgres.pl.html
@@ -104,16 +104,16 @@ or simple.</p>
<h2><a name="output_modes">Output Modes</a></h2>
<p>The output can be changed by use of the <code>--output</code> option. The default output
is nagios, although this can be changed at the top of the script if you wish. The
-current option choices are "nagios", "mrtg", and "simple". To avoid having to
+current option choices are <strong>nagios</strong>, <strong>mrtg</strong>, and <strong>simple</strong>. To avoid having to
enter the output argument each time, the type of output is automatically set
if no --output argument is given, and if the current directory has one of the
output options in its name. For example, creating a directory named mrtg and
-populating it with symlinks via the <a href="#symlinks"><code>--symlinks</code></a> argument would ensure that
+populating it with symlinks via the <em>--symlinks</em> argument would ensure that
any actions run from that directory will always default to an output of "mrtg"</p>
<p>
</p>
<h3><a name="nagios_output">Nagios output</a></h3>
-<p>The default output format is Nagios, which is a single line of information, along
+<p>The default output format is for Nagios, which is a single line of information, along
with four specific exit codes:</p>
<ol>
<li><strong><a name="ok" class="item">(OK)</a></strong>
@@ -127,8 +127,10 @@ with four specific exit codes:</p>
</ol>
<p>The output line is one of the words above, a colon, and then a short description of what
was measured. Additional statistics information, as well as the total time the command
-took, can be output as well: see the documentation on the arguments <em>--showperf</em>,
-<a href="#__perflimit">--perflimit</a>, and <a href="#__showtime">--showtime</a>.</p>
+took, can be output as well: see the documentation on the arguments
+<em><a href="#showperf_val">--showperf</a></em>,
+<em><a href="#perflimit_i">--perflimit</a></em>, and
+<em><a href="#showtime_val">--showtime</a></em>.</p>
<p>
</p>
<h3><a name="mrtg_output">MRTG output</a></h3>
@@ -139,7 +141,7 @@ The second line is an additional stat and is only used for some actions. The thi
an "uptime" and is not used. The fourth line is a description and usually indicates the name of
the database the stat from the first line was pulled from, but may be different depending on the
action.</p>
-<p>Some actions accept an optional <code>--mrtg</code> argument to further control the output.</p>
+<p>Some actions accept an optional <em>--mrtg</em> argument to further control the output.</p>
<p>See the documentation on each action for details on the exact MRTG output for each one.</p>
<p>
</p>
@@ -190,7 +192,7 @@ Instead, one should use a .pgpass file.</p>
</dd>
</li>
</dl>
-<p>The database connection options can be grouped: --host=a,b --host=c --port=1234 --port=3344
+<p>The database connection options can be grouped: <em>--host=a,b --host=c --port=1234 --port=3344</em>
would connect to a-1234, b-1234, and c-3344. Note that once set, an option
carries over until it is changed again.</p>
<p>Examples:</p>
@@ -273,9 +275,9 @@ VAL should be 0 or 1. The default is 1. Only takes effect if using Nagios output
<dd>
<p>Sets a limit as to how many items of interest are reported back when using the
-<strong>showperf</strong> option. This only has an effect for actions that return a large
+<em>showperf</em> option. This only has an effect for actions that return a large
number of items, such as <strong>table_size</strong>. The default is 0, or no limit. Be
-careful when using this with the <strong>--include</strong> or <strong>--exclude</strong> options, as
+careful when using this with the <em>--include</em> or <em>--exclude</em> options, as
those restrictions are done <em>after</em> the query has been run, and thus your
limit may not include the items you want. Only takes effect if using Nagios output mode.</p>
</dd>
@@ -284,7 +286,7 @@ limit may not include the items you want. Only takes effect if using Nagios outp
<dd>
<p>Determines if the time taken to run each query is shown in the output. VAL
-should be 0 or 1. The default is 1. No effect unless <strong>showperf</strong> is on.
+should be 0 or 1. The default is 1. No effect unless <em>showperf</em> is on.
Only takes effect if using Nagios output mode.</p>
</dd>
</li>
@@ -318,6 +320,12 @@ your psql location into the <code>$PSQL</code> variable, also near the top of th
other systems are supported yet.</p>
</dd>
</li>
+<dt><strong><a name="mrtg_val" class="item"><strong>--mrtg=VAL</strong></a></strong>
+
+<dd>
+<p>Used only for the MRTG or simple output, for a few specific actions.</p>
+</dd>
+</li>
</dl>
<p>
</p>
@@ -337,7 +345,7 @@ if use the option --symlinks</p>
perl check_postgres.pl --symlinks</pre>
<p>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 "--action=build_symlinks_force"</p>
-<p>Most actions take a <strong>--warning</strong> and an <strong>--critical</strong> option, indicating at what
+<p>Most actions take a <em>--warning</em> and a <em>--critical</em> 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
critical is an effective way to turn warnings off and always give a critical.</p>
@@ -348,15 +356,15 @@ critical is an effective way to turn warnings off and always give a critical.</p
<dd>
<p>Checks the current number of connections for one or more databases, and optionally
compares it to the maximum allowed, which is determined by the
-Postgres configuration variable <strong>max_connections</strong>. The <strong>--warning</strong> and
-<strong>--critical</strong> options can take one of three forms. First, a simple number can be
+Postgres configuration variable <strong>max_connections</strong>. The <em>--warning</em> and
+<em>--critical</em> options 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 <strong>max_connections</strong> 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 <strong>max_connections</strong>
-is reached. The default values for <strong>--warning</strong> and <strong>--critical</strong> are '90%' and '95%'.
+is reached. The default values for <em>--warning</em> and <em>--critical</em> are '90%' and '95%'.
You can also filter the databases by use of the
-<strong>--include</strong> and <strong>--exclude</strong> options. See the <a href="#basic_filtering">BASIC FILTERING</a> section
+<em>--include</em> and <em>--exclude</em> options. See the <a href="#basic_filtering">BASIC FILTERING</a> section
for more details.</p>
</dd>
<dd>
@@ -401,11 +409,11 @@ connections is output.</p>
of dead unused space taken up in a table or index. This space is usually reclaimed
by use of the VACUUM command.) This action requires that stats collection be
enabled on the target databases, and requires that ANALYZE is run frequently.
-The <strong>--include</strong> and <strong>--exclude</strong> options can be used to filter out which tables
+The <em>--include</em> and <em>--exclude</em> options can be used to filter out which tables
to look at. See the <a href="#basic_filtering">BASIC FILTERING</a> section for more details.</p>
</dd>
<dd>
-<p>The <strong>--warning</strong> and <strong>--critical</strong> options can be specified as sizes or percents.
+<p>The <em>--warning</em> and <em>--critical</em> options can be specified as sizes or percents.
Valid size units are bytes, kilobytes, megabytes, gigabytes, terabytes, and exabytes.
You can abbreviate all of those with the first letter. Items without units are
assumed to be 'bytes'. The default values are '1 GB' and '5 GB'. The value
@@ -416,7 +424,7 @@ used by the table and index, and what we compute that it should be.</p>
<p>Note that this action has two hard-coded values to avoid false alarms on
smaller relations. Tables must have at least 10 pages, and indexes at least 15,
before they can be considered by this test. If you really want to adjust these
-values, you can look for the variables <strong>$MINPAGES</strong> and <strong>$MINIPAGES</strong> at the top of the
+values, you can look for the variables <em>$MINPAGES</em> and <em>$MINIPAGES</em> at the top of the
<code>check_bloat</code> subroutine.</p>
</dd>
<dd>
@@ -462,7 +470,7 @@ times larger the relation is compared to how large it should be), just pass in <
<dd>
<p>Simply connects, issues a 'SELECT version()', and leaves.
-Takes no <strong>--warning</strong> or <strong>--critical</strong> options.</p>
+Takes no <em>--warning</em> or <em>--critical</em> options.</p>
</dd>
<dd>
<p>For MRTG output, simply outputs a 1 (good connection) or a 0 (bad connection) on the first line.</p>
@@ -506,7 +514,7 @@ bytes are assumed. The first column should be an integer representing the number
</dd>
<dd>
<p>Normally, an alert is triggered if the values returned are <strong>greater than</strong> or equal to the critical or warning
-value. However, an option of <strong>--reverse</strong> will trigger the alert if the returned value is
+value. However, an option of <em>--reverse</em> will trigger the alert if the returned value is
<strong>lower than</strong> or equal to the critical or warning value.</p>
</dd>
<dd>
@@ -544,10 +552,10 @@ to make it into a standard action that other people can use.</p>
<p>Checks the size of all databases and complains when they are too big.
There is no need to run this command more than once per database cluster.
Databases can be filtered with
-the <strong>--include</strong> and <strong>--exclude</strong> options. See the <a href="#basic_filtering">BASIC FILTERING</a> section
+the <em>--include</em> and <em>--exclude</em> options. See the <a href="#basic_filtering">BASIC FILTERING</a> section
for more details.
They can also be filtered by the owner of the database with the
-<strong>--includeuser</strong> and <strong>--excludeuser</strong> options.
+<em>--includeuser</em> and <em>--excludeuser</em> options.
See the <a href="#user_name_filtering">USER NAME FILTERING</a> section for more details.</p>
</dd>
<dd>
@@ -590,7 +598,7 @@ and the name of the database on the fourth line.</p>
<p>Checks on the available physical disk space used by Postgres. This action requires
that you have the executable "/bin/df" available to report on disk sizes, and it
also needs to be run as a superuser, so it can examine the <strong>data_directory</strong>
-setting inside of Postgres. The <strong>--warning</strong> and <strong>--critical</strong> options are
+setting inside of Postgres. The <em>--warning</em> and <em>--critical</em> options are
given in either sizes or percentages. If using sizes, the standard unit types
are allowed: bytes, kilobytes, gigabytes, megabytes, gigabytes, terabytes, or
exabytes. Each may be abbreviated to the first letter only; no units at all
@@ -647,22 +655,22 @@ and the name of the file system on the fourth line.</p>
<p>The actions <strong>table_size</strong> and <strong>index_size</strong> are simply variations of the
<strong>relation_size</strong> action, which checks for a relation that has grown too big.
Relations (in other words, tables and indexes) can be filtered with the
-<strong>--include</strong> and <strong>--exclude</strong> options. See the <a href="#basic_filtering">BASIC FILTERING</a> section
+<em>--include</em> and <em>--exclude</em> options. See the <a href="#basic_filtering">BASIC FILTERING</a> section
for more details. Relations can also be filtered by the user that owns them,
-by using the <strong>--includeuser</strong> and <strong>--excludeuser</strong> options.
+by using the <em>--includeuser</em> and <em>--excludeuser</em> options.
See the <a href="#user_name_filtering">USER NAME FILTERING</a> section for more details.</p>
</dd>
<dd>
-<p>The values for the <strong>--warning</strong> and <strong>--critical</strong> options are file sizes, and
+<p>The values for the <em>--warning</em> and <em>--critical</em> options are file sizes, and
may have units of bytes, kilobytes, megabytes, gigabytes, terabytes, or exabytes.
Each can be abbreviated to the first letter. If no units are given, bytes are
assumed. There are no default values: both the warning and the critical option
must be given. The return text shows the size of the largest relation found.</p>
</dd>
<dd>
-<p>If the <strong>--showperf</strong> option is enabled, <em>all</em> of the relations with their sizes
+<p>If the <em>--showperf</em> option is enabled, <em>all</em> of the relations with their sizes
will be given. To prevent this, it is recommended that you set the
-<strong>--perflimit</strong> option, which will cause the query to do a
+<em>--perflimit</em> option, which will cause the query to do a
<code>ORDER BY size DESC LIMIT (perflimit)</code>.</p>
</dd>
<dd>
@@ -704,14 +712,14 @@ and relation as the fourth line.</p>
table in one or more databases. Use of these actions requires that the target
database is version 8.3 or greater, or that the version is 8.2 and the
configuration variable <strong>stats_rows_level</strong> is enabled. Tables can be filtered with the
-<strong>--include</strong> and <strong>--exclude</strong> options. See the <a href="#basic_filtering">BASIC FILTERING</a> section
+<em>--include</em> and <em>--exclude</em> options. See the <a href="#basic_filtering">BASIC FILTERING</a> section
for more details.
Tables can also be filtered by their owner by use of the
-<strong>--includeuser</strong> and <strong>--excludeuser</strong> options.
+<em>--includeuser</em> and <em>--excludeuser</em> options.
See the <a href="#user_name_filtering">USER NAME FILTERING</a> section for more details.</p>
</dd>
<dd>
-<p>The units for <strong>--warning</strong> and <strong>--critical</strong> are specified as times.
+<p>The units for <em>--warning</em> and <em>--critical</em> are specified as times.
Valid units are seconds, minutes, hours, and days; all can be abbreviated
to the first letter. If no units are given, 'seconds' are assumed. The
default values are '1 day' and '2 days'. Please note that there are cases
@@ -774,11 +782,11 @@ be provided via the <--mrtg> option.</p>
<dd>
<p>Check the total number of locks on one or more databases. There is no
need to run this more than once per database cluster. Databases can be filtered
-with the <strong>--include</strong> and <strong>--exclude</strong> options. See the <a href="#basic_filtering">BASIC FILTERING</a> section
+with the <em>--include</em> and <em>--exclude</em> options. See the <a href="#basic_filtering">BASIC FILTERING</a> section
for more details.</p>
</dd>
<dd>
-<p>The <strong>--warning</strong> and <strong>--critical</strong> options can be specified as simple numbers,
+<p>The <em>--warning</em> and <em>--critical</em> options can be specified as simple numbers,
which represent the total number of locks, or they can be broken down by type of lock.
Valid lock names are <code>'total'</code>, <code>'waiting'</code>, or the name of a lock type used by Postgres.
These names are case-insensitive and do not need the "lock" part on the end,
@@ -812,7 +820,7 @@ checking, and ensures that the message shows up in the logs. It scans the
various log_* settings inside of Postgres to figure out where the logs should be.
If you are using syslog, it does a rough (but not foolproof) scan of
<em class="file">/etc/syslog.conf</em>. Alternatively, you can provide the name of the logfile
-with the <strong>--logfile</strong> option. This is especially useful if the logs have a
+with the <em>--logfile</em> option. This is especially useful if the logs have a
custom rotation scheme driven be an external program. The <strong>--logfile</strong> option
supports the following escape characters: <code>%Y %m %d %H</code>, which represent
the current year, month, date, and hour respectively. An error is always
@@ -843,11 +851,11 @@ failure, the fourth line will provide more detail on the failure encountered.</p
<dd>
<p>Checks how long a specific query takes to run, by executing a "EXPLAIN ANALYZE"
-against it. The <strong>--warning</strong> and <strong>--critical</strong> options are the maximum amount of
+against it. The <em>--warning</em> and <em>--critical</em> options are the maximum amount of
time the query should take. Valid units are seconds, minutes, and hours; any can be
abbreviated to the first letter. If no units are given, 'seconds' are assumed.
Both the warning and the critical option must be given. The name of the view or
-function to be run must be passed in to the <strong>--queryname</strong> option. It must consist
+function to be run must be passed in to the <em>--queryname</em> option. It must consist
of a single word (or schema.word), with optional parens at the end.</p>
</dd>
<dd>
@@ -868,13 +876,13 @@ line lists the database.</p>
<p>Checks the length of running queries on one or more databases. There is
no need to run this more than once on the same database cluster.
Databases can be filtered
-by using the <strong>--include</strong> and <strong>--exclude</strong> options. See the <a href="#basic_filtering">BASIC FILTERING</a>
+by using the <em>--include</em> and <em>--exclude</em> options. See the <a href="#basic_filtering">BASIC FILTERING</a>
section for more details. You can also filter on the user running the
-query with the <strong>--includeuser</strong> and <strong>--excludeuser</strong> options.
+query with the <em>--includeuser</em> and <em>--excludeuser</em> options.
See the <a href="#user_name_filtering">USER NAME FILTERING</a> section for more details.</p>
</dd>
<dd>
-<p>The values for the <strong>--warning</strong> and <strong>--critical</strong> options are amounts of
+<p>The values for the <em>--warning</em> and <em>--critical</em> options are amounts of
time, and default to '2 minutes' and '5 minutes' respectively. Valid units
are 'seconds', 'minutes', 'hours', or 'days'. Each may be written singular or
abbreviated to just the first letter. If no units are given, the unit is
@@ -912,7 +920,7 @@ line gives the name of the database.</p>
<p>Checks that master-slave replication is working to one or more slaves.
The slaves are specified the same as the normal databases, except with
the number 2 at the end of them, so "--port2" instead of "--port", etc.
-The values or the <strong>--warning</strong> and <strong>--critical</strong> options are units of time, and
+The values or the <em>--warning</em> and <em>--critical</em> options are units of time, and
at least one must be provided (no defaults). Valid units are 'seconds', 'minutes', 'hours',
or 'days'. Each may be written singular or abbreviated to just the first letter.
If no units are given, the units are assumed to be seconds.</p>
@@ -964,13 +972,13 @@ a time, an error is thrown.</p>
<p>Checks the length of open transactions on one or more databases.
There is no need to run this command more than once per database cluster.
Databases can be filtered by use of the
-<strong>--include</strong> and <strong>--exclude</strong> options. See the <a href="#basic_filtering">BASIC FILTERING</a> section
+<em>--include</em> and <em>--exclude</em> options. See the <a href="#basic_filtering">BASIC FILTERING</a> section
for more details. The owner of the transaction can also be filtered, by use of
-the <strong>--includeuser</strong> and <strong>--excludeuser</strong> options.
+the <em>--includeuser</em> and <em>--excludeuser</em> options.
See the <a href="#user_name_filtering">USER NAME FILTERING</a> section for more details.</p>
</dd>
<dd>
-<p>The values or the <strong>--warning</strong> and <strong>--critical</strong> options are units of time, and
+<p>The values or the <em>--warning</em> and <em>--critical</em> options are units of time, and
must be provided (no default). Valid units are 'seconds', 'minutes', 'hours',
or 'days'. Each may be written singular or abbreviated to just the first letter.
If no units are given, the units are assumed to be seconds.</p>
@@ -1002,11 +1010,11 @@ first line. The fourth line gives the name of the database.</p>
<dd>
<p>Checks the length of "idle in transaction" queries on one or more databases. There is
no need to run this more than once on the same database cluster. Databases can be filtered
-by using the <strong>--include</strong> and <strong>--exclude</strong> options. See the <a href="#basic_filtering">BASIC FILTERING</a>
+by using the <em>--include</em> and <em>--exclude</em> options. See the <a href="#basic_filtering">BASIC FILTERING</a>
section below for more details.</p>
</dd>
<dd>
-<p>The <strong>--warning</strong> and <strong>--critical</strong> options are given as units of time, and both must
+<p>The <em>--warning</em> and <em>--critical</em> options are given as units of time, and both must
be provided (there are no defaults). Valid units are 'seconds', 'minutes', 'hours',
or 'days'. Each may be written singular or abbreviated to just the first letter.
If no units are given, the unit are assumed to be seconds.</p>
@@ -1046,7 +1054,7 @@ then symlinks will be overwritten. The option --symlinks is a shorter way of say
This is done by generating a checksum of a sorted list of setting names and
their values. Note that different users in the same database may have different
checksums, due to ALTER USER usage, and due to the fact that superusers see more
-settings than ordinary users. Either the <strong>--warning</strong> or the <strong>--critical</strong> option
+settings than ordinary users. Either the <em>--warning</em> or the <em>--critical</em> option
should be given, but not both. The value of each one is the checksum, a
32-character hexadecimal value. You can run with the special <code>--critical=0</code> option
to find out an existing checksum.</p>
@@ -1074,11 +1082,11 @@ checksum must be provided as the <code>--mrtg</code> argument. The fourth line a
current checksum.</p>
</dd>
</li>
-<dt><strong><a name="timesync" class="item"><strong>timesync</strong> (symlink: <code>check_postgres_timesync</code>)</a></strong>
+<dt><strong><a name="timesync" class="item"><em>timesync</em> (symlink: <code>check_postgres_timesync</code>)</a></strong>
<dd>
<p>Compares the local system time with the time reported by one or more databases.
-The <strong>--warning</strong> and <strong>--critical</strong> options represent the number of seconds between
+The <em>--warning</em> and <em>--critical</em> options represent the number of seconds between
the two systems before an alert is given. If neither is specified, the default values
are used, which are '2' and '5'. The warning value cannot be greater than the critical
value. Due to the non-exact nature of this test, values of '0' or '1' are not recommended.</p>
@@ -1102,7 +1110,7 @@ time and the database time. The fourth line returns the name of the database.</p
<dd>
<p>Checks how close to transaction wraparound one or more databases are getting.
-The <strong>--warning</strong> and <strong>--critical</strong> options indicate the number of transactions
+The <em>--warning</em> and <em>--critical</em> options indicate the number of transactions
left, and must be a positive integer. If either option is not given, the default
values of 1.3 and 1.4 billion are used. There is no need to run this command
more than once per database cluster. For a more detailed discussion of what this
@@ -1138,7 +1146,7 @@ while line 4 indicates which database it is.</p>
off of your <strong>data_directory</strong>, sometimes as a symlink to another physical disk for
performance reasons. This action must be run as a superuser, in order to access the
contents of the <em class="file">pg_xlog</em> directory. The minimum version to use this action is
-Postgres 8.1. The <strong>--warning</strong> and <strong>--critical</strong> options are simply the number of
+Postgres 8.1. The <em>--warning</em> and <em>--critical</em> options are simply the number of
files in the <em class="file">pg_xlog</em> directory. What number to set this to will vary, but a general
guideline is to put a number slightly higher than what is normally there, to catch
problems early.</p>
@@ -1164,7 +1172,7 @@ out of space, at which point Postgres will shut down.</p>
<dd>
<p>Checks that the required version of Postgres is running. The
-<strong>--warning</strong> and <strong>--critical</strong> options (only one is required) must be of
+<em>--warning</em> and <em>--critical</em> options (only one is required) must be of
the format <strong>X.Y</strong> or <strong>X.Y.Z</strong> where <strong>X</strong> is the major version number,
<strong>Y</strong> is the minor version number, and <strong>Z</strong> is the revision.</p>
</dd>
@@ -1190,7 +1198,7 @@ fourth line indicates the current version. The version must be provided via the
</p>
<hr />
<h1><a name="basic_filtering">BASIC FILTERING</a></h1>
-<p>The options <strong>--include</strong> and <strong>--exclude</strong> can be combined to limit which
+<p>The options <em>--include</em> and <em>--exclude</em> can be combined to limit which
things are checked, depending on the action. The name of the database can
be filtered when using the following actions:
backends, database_size, locks, query_time, txn_idle, and txn_time.
@@ -1202,7 +1210,7 @@ The name of a file system can be filtered when using the disk_space action.</p>
<p>If only an include option is given, then ONLY those entries that match will be
checked. However, if given both exclude and include, the exclusion is done first,
and the inclusion after, to reinstate things that may have been excluded. Both
-<strong>--include</strong> and <strong>--exclude</strong> can be given multiple times,
+<em>--include</em> and <em>--exclude</em> can be given multiple times,
and/or as comma-separated lists. A leading tilde will match the following word
as a regular expression.</p>
<p>To match a schema, end the search term with a single period. Leading tildes can
@@ -1237,9 +1245,9 @@ or which are named 'sql_settings' or 'green'. Specifically check items with the
</p>
<hr />
<h1><a name="user_name_filtering">USER NAME FILTERING</a></h1>
-<p>The options <strong>--includeuser</strong> and <strong>--excludeuser</strong> can be used on some actions
+<p>The options <em>--includeuser</em> and <em>--excludeuser</em> can be used on some actions
to only examine database objects owned by (or not owned by) one or more users.
-An <strong>--includeuser</strong> option always trumps an <strong>--excludeuser</strong> option. You can
+An <em>--includeuser</em> option always trumps an <em>--excludeuser</em> option. You can
give each option more than once for multiple users, or you can give a
comma-separated list. The actions that currently use these options are:</p>
<dl>
@@ -1278,7 +1286,7 @@ comma-separated list. The actions that currently use these options are:</p>
<hr />
<h1><a name="test_mode">TEST MODE</a></h1>
<p>To help in setting things up, this program can be run in a "test mode" by
-specifying the <strong>--test</strong> option. This will perform some basic tests to
+specifying the <em>--test</em> option. This will perform some basic tests to
make sure that the databases can be contacted, and that certain per-action
prerequisites are met, such as whether the user is a superuser, if the version
of Postgres is new enough, and if stats_row_level is enabled.</p>
@@ -1310,7 +1318,7 @@ instead of symlinks, so that the plugin only gets compiled one time.</p>
</dl>
<p>The <strong>settings_checksum</strong> action requires the <strong>Digest::MD5</strong> module.</p>
<p>Some actions require access to external programs. If psql is not explicitly
-specified, the command <strong>which</strong> is used to find it. The program <strong>/bin/df</strong>
+specified, the command <strong><code>which</code></strong> is used to find it. The program <strong><code>/bin/df</code></strong>
is needed by the <strong>check_disk_space</strong> action.</p>
<p>
</p>
@@ -1335,7 +1343,7 @@ feature requests, and commit notices, send email to <a href="mailto:check_postgr
<h1><a name="history">HISTORY</a></h1>
<p>Items not specifically attributed are by Greg Sabino Mullane.</p>
<dl>
-<dt><strong><a name="0" class="item"><strong>Version 2.0.0</strong> (July 2008)</a></strong>
+<dt><strong><a name="0" class="item"><strong>Version 2.0.0</strong> (July 15, 2008)</a></strong>
<dd>
<p>Add support for MRTG and "simple" output options.
--
1.5.5.4
More information about the Check_postgres
mailing list