503 |
testing is as follows (keywords are in capital and optional |
testing is as follows (keywords are in capital and optional |
504 |
statements in [brackets]) for networked ports, |
statements in [brackets]) for networked ports, |
505 |
|
|
506 |
[HOST hostname] PORT number [TYPE {TCP|UDP|TCPSSL}] |
[HOST hostname] PORT number |
507 |
|
[TYPE {TCP|UDP|TCPSSL [CERTMD5 md5sum]}] |
508 |
[PROTO(COL) {name} [REQUEST {"/path"}]] |
[PROTO(COL) {name} [REQUEST {"/path"}]] |
509 |
|
|
510 |
or for unix sockets, |
or for unix sockets, |
524 |
|
|
525 |
port 53 use type udp ('use' is a noise keyword) |
port 53 use type udp ('use' is a noise keyword) |
526 |
|
|
527 |
|
The I<TCPSSL> statement accepts optionally the md5 sum of the |
528 |
|
server's certificate. The md5 sum is matched against the one |
529 |
|
delivered by the server. In case they do not match the |
530 |
|
connection test fails. |
531 |
|
|
532 |
In case a server is listening to a unix socket called |
In case a server is listening to a unix socket called |
533 |
/var/run/mysocket, the following statement can be used: |
/var/run/mysocket, the following statement can be used: |
534 |
|
|
924 |
connection when testing the port. |
connection when testing the port. |
925 |
udp Specifies that monit should use a UDP socket |
udp Specifies that monit should use a UDP socket |
926 |
type (datagram) when testing the port. |
type (datagram) when testing the port. |
927 |
|
certmd5 The md5 sum of a certificate a ssl forged |
928 |
|
server has to deliver. |
929 |
proto(col) This keyword specifies the type of service |
proto(col) This keyword specifies the type of service |
930 |
found at the port. monit knows at the moment |
found at the port. monit knows at the moment |
931 |
how to speak HTTP, SMPT, FTP, POP and IMAP. |
how to speak HTTP, SMPT, FTP, POP and IMAP. |