diff options
author | Konstantinos Natsakis <5933427+knatsakis@users.noreply.github.com> | 2019-11-06 21:41:00 +0200 |
---|---|---|
committer | GitHub <noreply@github.com> | 2019-11-06 21:41:00 +0200 |
commit | 727fe4ebaca0c468bf3aceef0918acbb1280d49e (patch) | |
tree | 0843715bd1d937eb8161f6c6938e90f62dc57683 /packaging | |
parent | b1a69530104a3569b33f6a8f5075e32ad621379d (diff) |
Remove documentation about kickstart-static64.sh and netdata updater (#7262)
Until the netdata updater starts working with kickstart-static64.sh with
issue #7197
Diffstat (limited to 'packaging')
-rw-r--r-- | packaging/installer/UPDATE.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/packaging/installer/UPDATE.md b/packaging/installer/UPDATE.md index b76cba2815..ab5b558f76 100644 --- a/packaging/installer/UPDATE.md +++ b/packaging/installer/UPDATE.md @@ -46,7 +46,7 @@ _Please, consider the risks of running an auto-update. Something can always go w Calling the `netdata-installer.sh` with the `--auto-update` or `-u` option will create the `netdata-updater` script under either `/etc/cron.daily/`, or `/etc/periodic/daily/`. Whenever the `netdata-updater` is executed, it checks if a newer nightly build is available and then handles the download, installation and Netdata restart. -Note that after Jan 2019, the `kickstart.sh` one-liner `bash <(curl -Ss https://my-netdata.io/kickstart.sh)` calls the `netdata-installer.sh` with the auto-update option. So if you just run the one-liner without options once, your Netdata will be kept auto-updated. The same applies to the `kickstart-static64.sh` one-liner since Oct 2019. +Note that after Jan 2019, the `kickstart.sh` one-liner `bash <(curl -Ss https://my-netdata.io/kickstart.sh)` calls the `netdata-installer.sh` with the auto-update option. So if you just run the one-liner without options once, your Netdata will be kept auto-updated. ## You downloaded a binary package |