summaryrefslogtreecommitdiffstats
path: root/packaging
diff options
context:
space:
mode:
authorChris Akritidis <43294513+cakrit@users.noreply.github.com>2019-02-19 13:36:51 +0100
committerGitHub <noreply@github.com>2019-02-19 13:36:51 +0100
commit797c9a9efb2a271b6f0d709f8c4b2fc9b5c93835 (patch)
tree044a93ddfb368a10f3c43d03ab28a9ec21d5d5e6 /packaging
parent4e5967aa6fb97a39d7774509c07bbd315b63454c (diff)
Uninstall instruction improvements (#5414)
Fix to kickstart command and a bit more clarity on binary packages
Diffstat (limited to 'packaging')
-rw-r--r--packaging/installer/UPDATE.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/packaging/installer/UPDATE.md b/packaging/installer/UPDATE.md
index 92571b48de..c93ebf9b48 100644
--- a/packaging/installer/UPDATE.md
+++ b/packaging/installer/UPDATE.md
@@ -32,7 +32,7 @@ Keep in mind, netdata may now have new features, or certain old features may now
The `kickstart.sh` one-liner will do a one-time update to the latest nightly build, if executed as follows:
```
-bash <(curl -Ss https://my-netdata.io/kickstart.sh --no-updates)
+bash <(curl -Ss https://my-netdata.io/kickstart.sh) --no-updates
```
### Auto-update
@@ -47,7 +47,7 @@ Note that after Jan 2019, the `kickstart.sh` one-liner `bash <(curl -Ss https://
## You downloaded a binary package
-If you installed it from a binary package, the best way is to **obtain a newer copy** from the source you got it in the first place.
+If you installed it from a binary package, the best way is to **obtain a newer copy** from the source you got it in the first place. This includes the static binary installation via `kickstart-base64.sh`, which would need to be executed again.
If a newer version of netdata is not available from the source you got it, we suggest to uninstall the version you have and follow the [installation](README.md) instructions for installing a fresh version of netdata.