From 778fda7aea63058558664b3d707b66cc141229b0 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Michael=20H=C3=B6=C3=9F?= Date: Wed, 23 Feb 2022 14:58:40 +0100 Subject: [PATCH] README fixes --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index eb80223..1a46df9 100644 --- a/README.md +++ b/README.md @@ -14,7 +14,7 @@ But if you want to ensure - has the expected output - only one instances executes in parallel -and want all this to be monitored with your CheckMK, you have to add a lot of plumping code. +and want all this to be monitored with your CheckMK, you have to add a lot of plumbing code. jobwatch helps to migitate this problem. It wraps the execution of your script, and does all the rest for you, by providing output, which can be fed to CheckMK by the @@ -67,8 +67,8 @@ The config-config dir is When run as ## Deploying jobwatch - Compile the go program, if required, the src-dir: `go get .;go build .` -- `cp jobwatch /usr/loca/bin` -- `ln -s /usr/local/bin /usr/lib/check_agent/plugins` +- `cp jobwatch /usr/local/bin` +- `ln -s /usr/local/bin/jobwatch /usr/lib/check_agent/plugins` On the check-mk server just deploy the provede .mkp, no further config there is currently needed