valitydev/salt
14
0
Fork 0
mirror of https://github.com/valitydev/salt.git synced 2024-11-07 08:58:59 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Schedule documentation update.

Browse Source
This commit is contained in:
Carl Meyers 2014-08-18 21:20:54 -07:00
parent 5ba675f42b
commit 7c4ce67d28
1 changed files with 4 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
doc/topics/jobs/schedule.rst
View File

@ -4,7 +4,7 @@ executions on minions or the master. The schedule system exposes the execution
of any execution function on minions or any runner on the master.
Scheduling is enabled via the ``schedule`` option on either the master or minion
config files, or via a minion's pillar data.
config files, or via a minion's pillar data. Schedules that are impletemented via pillar data, only need to refresh the minion's pillar data, for example by using ``saltutil.refresh_pillar``. Schedules implemented in the master or minion config have to restart the application in order for the schedule to be implemented.
.. note::
@ -12,6 +12,8 @@ config files, or via a minion's pillar data.
running on the master the functions reference runner functions, when
running on the minion the functions specify execution functions.
A scheduled run has no output on the minion unless the config is set to info level or higher. Refer to :doc:`minion logging settings <ref/configuration/minion>`.
Specify ``maxrunning`` to ensure that there are no more than N copies of
a particular routine running. Use this for jobs that may be long-running
and could step on each other or otherwise double execute. The default for
@ -150,7 +152,7 @@ States
- 'logger -t salt < /proc/loadavg'
kwargs:
stateful: False
shell: True
shell: \bin\sh
Highstates
==========