diff options
| author | Bernhard Posselt <dev@bernhard-posselt.com> | 2016-05-05 16:42:12 +0300 |
|---|---|---|
| committer | Bernhard Posselt <dev@bernhard-posselt.com> | 2016-05-05 16:42:12 +0300 |
| commit | 99d4f4d981008a93312f4ed8999b8b46925fc96e (patch) | |
| tree | 986985f3425b3338ff9cf137b5c1b278cca28fb4 | |
| parent | 1668296d90b580316c0dd52521e18b95bcae310b (diff) | |
changelog fix
| -rw-r--r-- | README.rst | 4 |
1 files changed, 2 insertions, 2 deletions
@@ -259,9 +259,9 @@ If you still have to use a self-signed certificate no matter what, don't patch t Can I Run The Updater Using Cron ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -Yes, you can by using the **--mode singlerun** parameter which will exit after an update. +Yes, you can by using the **--mode singlerun** parameter which will exit after one full update. -However it's your job to ensure, that the job will not be executed more than once at the same time. This **can take down your system and/or server** since each new updater will slow down the previous ones causing more updaters to be spawned. +However it's your job to ensure, that the job will not be executed more than once at the same time. If update jobs overlap, they **can take down your system and/or server** since each new updater will slow down the previous ones causing more updaters to be spawned. If you can not ensure that the updater is run only one at a time use the default mode (**--mode endless**). This mode runs the update in a loop. You can control the update frequency through the **--interval** parameter (or **interval** using a config file). The updater works in the following way: * If a full update takes longer than the passed interval, another update will be run immediately afterwards |