|
1 |
| -check_postgres is Copyright (C) 2007-2013, Greg Sabino Mullane |
| 1 | +check_postgres |
| 2 | +============== |
| 3 | + |
| 4 | +[](https://travis-ci.com/bucardo/check_postgres) |
2 | 5 |
|
3 | 6 | This is check_postgres, a monitoring tool for Postgres.
|
4 | 7 |
|
5 | 8 | The most complete and up to date information about this script can be found at:
|
6 | 9 |
|
7 |
| -http://bucardo.org/check_postgres/ |
8 |
| - |
9 |
| -You should go check there right now to make sure you are installing |
10 |
| -the latest version! |
| 10 | +https://bucardo.org/check_postgres/ |
11 | 11 |
|
12 | 12 | This document will cover how to install the script.
|
13 | 13 |
|
14 |
| -* Quick method: |
| 14 | +Quick method |
| 15 | +------------ |
15 | 16 |
|
16 |
| -For the impatient Nagios admin, just copy the "check_postgres.pl" file |
17 |
| -to your Nagios scripts directory, and perhaps symlink entries to that |
| 17 | +For the impatient Nagios admin, just copy the "check_postgres.pl" file |
| 18 | +to your Nagios scripts directory, and perhaps symlink entries to that |
18 | 19 | file by:
|
19 | 20 |
|
20 |
| -cd <the directory you just copied the file to> |
21 |
| -mkdir postgres |
22 |
| -cd postgres |
23 |
| -perl ../check_postgres.pl --symlinks |
| 21 | + cd <the directory you just copied the file to> |
| 22 | + mkdir postgres |
| 23 | + cd postgres |
| 24 | + perl ../check_postgres.pl --symlinks |
24 | 25 |
|
25 | 26 | Then join the announce mailing list (see below)
|
26 | 27 |
|
27 |
| - |
28 |
| -* Complete method: |
| 28 | +Complete method |
| 29 | +--------------- |
29 | 30 |
|
30 | 31 | The better way to install this script is via the standard Perl process:
|
31 | 32 |
|
32 |
| -perl Makefile.PL |
33 |
| -make |
34 |
| -make test |
35 |
| -make install |
| 33 | + perl Makefile.PL |
| 34 | + make |
| 35 | + env -i make test |
| 36 | + make install |
36 | 37 |
|
37 |
| -The last step usually needs to be done as the root user. You may want to |
38 |
| -copy the script to a place that makes more sense for Nagios, if using it |
| 38 | +The last step usually needs to be done as the root user. You may want to |
| 39 | +copy the script to a place that makes more sense for Nagios, if using it |
39 | 40 | for that purpose. See the "Quick" instructions above.
|
40 | 41 |
|
41 |
| -For 'make test', please report any failing tests to check_postgres@bucardo.org. |
42 |
| -The tests need to have some standard Postgres binaries available, such as |
43 |
| -'initdb', 'psql', and 'pg_ctl'. If these are not in your path, or you want to |
44 |
| -use specific ones, please set the environment variable PGBINDIR first. |
| 42 | +For `make test`, please report any failing tests to check_postgres@bucardo.org. |
| 43 | +The tests need to have some standard Postgres binaries available, such as |
| 44 | +`initdb`, `psql`, and `pg_ctl`. If these are not in your path, or you want to |
| 45 | +use specific ones, please set the environment variable `PGBINDIR` first. More |
| 46 | +details on running the testsuite are available in `README.dev`. |
45 | 47 |
|
46 |
| -Once 'make install' has been done, you should have access to the complete |
| 48 | +Once `make install` has been done, you should have access to the complete |
47 | 49 | documentation by typing:
|
48 | 50 |
|
49 |
| -man check_postgres |
| 51 | + man check_postgres |
50 | 52 |
|
51 | 53 | The HTML version of the documentation is also available at:
|
52 | 54 |
|
53 |
| -http://bucardo.org/check_postgres/check_postgres.pl.html |
| 55 | +https://bucardo.org/check_postgres/check_postgres.pl.html |
54 | 56 |
|
55 |
| -* Mailing lists |
| 57 | +Mailing lists |
| 58 | +------------- |
56 | 59 |
|
57 |
| -The final step should be to subscribe to the low volume check_postgres-announce |
58 |
| -mailing list, so you learn of new versions and important changes. Information |
| 60 | +The final step should be to subscribe to the low volume check_postgres-announce |
| 61 | +mailing list, so you learn of new versions and important changes. Information |
59 | 62 | on joining can be found at:
|
60 | 63 |
|
61 | 64 | https://mail.endcrypt.com/mailman/listinfo/check_postgres-announce
|
62 | 65 |
|
63 |
| -General questions and development issues are discussed on the check_postgres list, |
| 66 | +General questions and development issues are discussed on the check_postgres list, |
64 | 67 | which we recommend people join as well:
|
65 | 68 |
|
66 | 69 | https://mail.endcrypt.com/mailman/listinfo/check_postgres
|
67 | 70 |
|
68 | 71 | Development happens via git. You can check out the repository by doing:
|
69 | 72 |
|
70 |
| -git clone git://bucardo.org/check_postgres.git |
71 |
| - |
72 |
| -All changes are sent to the commit list: |
73 |
| - |
74 |
| -https://mail.endcrypt.com/mailman/listinfo/check_postgres-commit |
75 |
| - |
76 |
| -COPYRIGHT: |
77 |
| ----------- |
| 73 | + https://github.com/bucardo/check_postgres |
| 74 | + git clone https://github.com/bucardo/check_postgres.git |
78 | 75 |
|
79 |
| - Copyright (c) 2007-2013 Greg Sabino Mullane |
| 76 | +COPYRIGHT |
| 77 | +--------- |
80 | 78 |
|
| 79 | + Copyright 2007 - 2021 Greg Sabino Mullane |
81 | 80 |
|
82 |
| -LICENSE INFORMATION: |
83 |
| --------------------- |
| 81 | +LICENSE INFORMATION |
| 82 | +------------------- |
84 | 83 |
|
85 |
| -Redistribution and use in source and binary forms, with or without |
| 84 | +Redistribution and use in source and binary forms, with or without |
86 | 85 | modification, are permitted provided that the following conditions are met:
|
87 | 86 |
|
88 |
| - 1. Redistributions of source code must retain the above copyright notice, |
| 87 | + 1. Redistributions of source code must retain the above copyright notice, |
89 | 88 | this list of conditions and the following disclaimer.
|
90 |
| - 2. Redistributions in binary form must reproduce the above copyright notice, |
91 |
| - this list of conditions and the following disclaimer in the documentation |
| 89 | + 2. Redistributions in binary form must reproduce the above copyright notice, |
| 90 | + this list of conditions and the following disclaimer in the documentation |
92 | 91 | and/or other materials provided with the distribution.
|
93 | 92 |
|
94 |
| -THIS SOFTWARE IS PROVIDED BY THE AUTHOR "AS IS" AND ANY EXPRESS OR IMPLIED |
95 |
| -WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF |
96 |
| -MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO |
| 93 | +THIS SOFTWARE IS PROVIDED BY THE AUTHOR "AS IS" AND ANY EXPRESS OR IMPLIED |
| 94 | +WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF |
| 95 | +MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO |
97 | 96 | EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
|
98 |
| -EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT |
99 |
| -OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS |
100 |
| -INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN |
101 |
| -CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING |
102 |
| -IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY |
| 97 | +EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT |
| 98 | +OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS |
| 99 | +INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN |
| 100 | +CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING |
| 101 | +IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY |
103 | 102 | OF SUCH DAMAGE.
|
0 commit comments