From: Christoph Berg Date: Fri, 30 Dec 2016 22:14:52 +0000 (+0100) Subject: Clarify that only one action is run per invocation. X-Git-Url: http://git.postgresql.org/gitweb/?a=commitdiff_plain;h=761e2602e33c604b5068f24e6bf1d32b1d978ae9;p=check_postgres.git Clarify that only one action is run per invocation. The old wording could be interpreted as allowing several actions to be executed in parallel. Close #115. --- diff --git a/check_postgres.pl b/check_postgres.pl index 76514448f..217e08222 100755 --- a/check_postgres.pl +++ b/check_postgres.pl @@ -8721,7 +8721,7 @@ will override any such detection. =head1 ACTIONS -The script runs one or more actions. This can either be done with the --action +The action to be run is selected using the --action flag, or by using a symlink to the main file that contains the name of the action inside of it. For example, to run the action "timesync", you may either issue: @@ -8732,12 +8732,12 @@ or use a program named: check_postgres_timesync All the symlinks are created for you in the current directory -if use the option --symlinks +if use the option --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 "--action=build_symlinks_force" +and is a symlink, you can force it to overwrite by using "--action=build_symlinks_force". Most actions take a I<--warning> and a I<--critical> option, indicating at what point we change from OK to WARNING, and what point we go to CRITICAL. Note that