Current File : //lib/python2.7/site-packages/salt/states/cron.pyo
�
���^c @@ s d Z d d l m Z m Z m Z d d l Z d d l Z d d l m Z m
Z
d d l m Z d � Z
d d d d d d d d d d � Z d d � Z d � Z d
d d d d d d e e d d �
Z d
e d d
� Z d d d
d d e d d d � Z d d
d � Z d
d � Z d S( uY
Management of cron, the Unix command scheduler
==============================================
Cron declarations require a number of parameters. The following are the
parameters used by Salt to define the various timing values for a cron job:
* ``minute``
* ``hour``
* ``daymonth``
* ``month``
* ``dayweek`` (0 to 6 are Sunday through Saturday, 7 can also be used for
Sunday)
.. warning::
Any timing arguments not specified take a value of ``*``. This means that
setting ``hour`` to ``5``, while not defining the ``minute`` param, will
result in Salt adding a job that will execute every minute between 5 and 6
A.M.!
Additionally, the default user for these states is ``root``. Therefore, if
the cron job is for another user, it is necessary to specify that user with
the ``user`` parameter.
A long time ago (before 2014.2), when making changes to an existing cron job,
the name declaration is the parameter used to uniquely identify the job,
so if an existing cron that looks like this:
.. code-block:: yaml
date > /tmp/crontest:
cron.present:
- user: root
- minute: 5
Is changed to this:
.. code-block:: yaml
date > /tmp/crontest:
cron.present:
- user: root
- minute: 7
- hour: 2
Then the existing cron will be updated, but if the cron command is changed,
then a new cron job will be added to the user's crontab.
The current behavior is still relying on that mechanism, but you can also
specify an identifier to identify your crontabs:
.. code-block:: yaml
date > /tmp/crontest:
cron.present:
- identifier: SUPERCRON
- user: root
- minute: 7
- hour: 2
.. versionadded:: 2014.1.2
And, some months later, you modify it:
.. code-block:: yaml
superscript > /tmp/crontest:
cron.present:
- identifier: SUPERCRON
- user: root
- minute: 3
- hour: 4
.. versionadded:: 2014.1.2
The old **date > /tmp/crontest** will be replaced by
**superscript > /tmp/crontest**.
Additionally, Salt also supports running a cron every ``x minutes`` very similarly to the Unix
convention of using ``*/5`` to have a job run every five minutes. In Salt, this
looks like:
.. code-block:: yaml
date > /tmp/crontest:
cron.present:
- user: root
- minute: '*/5'
The job will now run every 5 minutes.
Additionally, the temporal parameters (minute, hour, etc.) can be randomized by
using ``random`` instead of using a specific value. For example, by using the
``random`` keyword in the ``minute`` parameter of a cron state, the same cron
job can be pushed to hundreds or thousands of hosts, and they would each use a
randomly-generated minute. This can be helpful when the cron job accesses a
network resource, and it is not desirable for all hosts to run the job
concurrently.
.. code-block:: yaml
/path/to/cron/script:
cron.present:
- user: root
- minute: random
- hour: 2
.. versionadded:: 0.16.0
Since Salt assumes a value of ``*`` for unspecified temporal parameters, adding
a parameter to the state and setting it to ``random`` will change that value
from ``*`` to a randomized numeric value. However, if that field in the cron
entry on the minion already contains a numeric value, then using the ``random``
keyword will not modify it.
Added the opportunity to set a job with a special keyword like '@reboot' or
'@hourly'. Quotes must be used, otherwise PyYAML will strip the '@' sign.
.. code-block:: yaml
/path/to/cron/script:
cron.present:
- user: root
- special: '@hourly'
The script will be executed every reboot if cron daemon support this option.
.. code-block:: yaml
/path/to/cron/otherscript:
cron.absent:
- user: root
- special: '@daily'
This counter part definition will ensure than a job with a special keyword
is not set.
i ( t absolute_importt unicode_literalst print_functionN( t
_needs_changet
_cron_matched( t sixc C@ s d t k r t St d f Sd S( Nu
cron.list_tabu cron module could not be loaded( t __salt__t Truet False( ( ( s4 /usr/lib/python2.7/site-packages/salt/states/cron.pyt __virtual__� s c
C@ s� | d k r$ t j | � j � } n | d k rH t j | � j � } n | d k rl t j | � j � } n | d k r� t j | � j � } n | d k r� t j | � j � } n | d k r� t j | � } n | d k r� | t k } n | d k r t j | � } n t d | � } |
d k r�xp| d D]� } t | | | � r2t g | d | f | d | f | d | f | d | f | d | f | d | f | d | f | d
| f | d | f f D] \ }
} t |
| � ^ q�� r�d Sd
Sq2Wn� x� | d D]� } t | | | � rt g | d |
f | d | f | d | f | d
| f | d | f f D] \ }
} t |
| � ^ qj� r�d Sd
SqWd S( u
Return the changes
u
cron.list_tabu cronsu minuteu houru daymonthu monthu dayweeku
identifieru cmdu commentu commentedu updateu presentu specialu specu absentN( t NoneR t text_typet lowerR R R t anyR ( t usert cmdt minutet hourt daymontht montht dayweekt commentt commentedt
identifiert specialt lstt cront xt y( ( s4 /usr/lib/python2.7/site-packages/salt/states/cron.pyt _check_cron� sN 5
5c C@ sf | d k r d } n t d | � } x: | d D]. } | | d k r0 | | d k rZ d Sd Sq0 Wd S(
u(
Return the environment changes
u u
cron.list_tabu envu nameu valueu updateu presentu absentN( R
R ( R t namet valueR t env( ( s4 /usr/lib/python2.7/site-packages/salt/states/cron.pyt _check_cron_env� s c C@ s� d } t d d k r% d } d } ni t d d k rD d } d } nJ t d d k rc d } d
} n+ t d d k r� d } d } n d } d
} | | | f S( uG
Returns the proper group owner and path to the cron directory
u rootu osu FreeBSDu wheelu /var/cron/tabsu OpenBSDu crontabu os_familyu Solarisu /var/spool/cron/crontabsu MacOSu /usr/lib/cron/tabsu /var/spool/cron( t
__grains__( t ownert groupt crontab_dir( ( s4 /usr/lib/python2.7/site-packages/salt/states/cron.pyt _get_cron_info� s u rootu *c C@ sQ | j � } | t k r! | } n i i d 6d d 6| d 6t d 6} t d rt | d | d | d | d
| d | d | d
| d | d | d |
�
} d | d <| d k r� d j | � | d <nN | d k r� t | d <d j | � | d <n" | d k rd j | � | d <n | S|
d k rkt d d | d | d | d
| d | d | d | d
| d | d | �
}
n1 t d d | d |
d | d
| d | d | � }
|
d k r�d j | � | d <| S|
d k r�d j | | � | d <i | | 6| d <| S|
d k r*d j | � | d <i | | 6| d <| Sd j | | |
� | d <t | d <| S( u�
Verifies that the specified cron job is present for the specified user.
It is recommended to use `identifier`. Otherwise the cron job is installed
twice if you change the name.
For more advanced information about what exactly can be set in the cron
timing parameters, check your cron system's documentation. Most Unix-like
systems' cron documentation can be found via the crontab man page:
``man 5 crontab``.
name
The command that should be executed by the cron job.
user
The name of the user whose crontab needs to be modified, defaults to
the root user
minute
The information to be set into the minute section, this can be any
string supported by your cron system's the minute field. Default is
``*``
hour
The information to be set in the hour section. Default is ``*``
daymonth
The information to be set in the day of month section. Default is ``*``
month
The information to be set in the month section. Default is ``*``
dayweek
The information to be set in the day of week section. Default is ``*``
comment
User comment to be added on line previous the cron job
commented
The cron job is set commented (prefixed with ``#DISABLED#``).
Defaults to False.
.. versionadded:: 2016.3.0
identifier
Custom-defined identifier for tracking the cron line for future crontab
edits. This defaults to the state name
special
A special keyword to specify periodicity (eg. @reboot, @hourly...).
Quotes must be used, otherwise PyYAML will strip the '@' sign.
.. versionadded:: 2016.3.0
u changesu u commentu nameu resultu testR R R R R R R R R R u absentu Cron {0} is set to be addedu presentu Cron {0} already presentu updateu Cron {0} is set to be updatedu cron.set_jobR u cron.set_specialu newu Cron {0} added to {1}'s crontabu updatedu Cron {0} updatedu6 Cron {0} for user {1} failed to commit with error
{2}N( t stripR R t __opts__R R
t formatR ( R R R R R R R R R R R t rett statust data( ( s4 /usr/lib/python2.7/site-packages/salt/states/cron.pyt present sx ?
c K@ s� | j � } | t k r! | } n i | d 6t d 6i d 6d d 6} t d r� t | | d | �} d | d <| d k r� t | d <d j | � | d <n. | d
k s� | d k r� d j | � | d <n | S| d k r� t d
| | d | �} n t d | | d | d | �} | d k r4d j | � | d <| S| d k rkd j | | � | d <i | | 6| d <| Sd j | | | � | d <t | d <| S( ug
Verifies that the specified cron job is absent for the specified user; only
the name is matched when removing a cron job.
name
The command that should be absent in the user crontab.
user
The name of the user whose crontab needs to be modified, defaults to
the root user
identifier
Custom-defined identifier for tracking the cron line for future crontab
edits. This defaults to the state name
special
The special keyword used in the job (eg. @reboot, @hourly...).
Quotes must be used, otherwise PyYAML will strip the '@' sign.
u nameu resultu changesu u commentu testR u absentu Cron {0} is absentu presentu updateu Cron {0} is set to be removedu cron.rm_jobu cron.rm_specialR u Cron {0} already absentu removedu# Cron {0} removed from {1}'s crontabu5 Cron {0} for user {1} failed to commit with error {2}N( R' R R R( R R
R) R ( R R R R t kwargsR* R+ R, ( ( s4 /usr/lib/python2.7/site-packages/salt/states/cron.pyt absent� s>
u c K@ s+ d }
y t d | � d d } Wn= t k
ra i i d 6d j | � d 6| d 6t d 6} | SXt j j j � }
t j j j |
d
� �T } t d | � } | j d � s� d
j | � } n | j
t j j j | � � Wd QXi i d 6d d 6| d 6t
d 6} | } | rMt j |
� j d k rMd j | � | d <t j |
� | St d r�t d d |
d | d | d | d | d | d |
d g d | d | d | d t | � } | \ | d <| d <t j |
� | St d | | t � \ } } yk t d d |
d | d | d | d | d | d | d |
d g d t d | d | d! t | �
\ } } } Wn; t k
r�} t | d <i | d <d" j | � | d <| SX| r�| | d <t | d <t j |
� | SyS t d# d |
d$ | d% | d | d& | d | d | d |
d g d t d' | � } Wn; t k
rT} t | d <i | d <d" j | � | d <| SXd } d( | d k r�t d) | |
� } | d* d k r�d+ j | � | d <t
| d <| d | d <qd, j | |
| d- � | d <t | d <i | d <n* | d rd. j | � | d <i | d <n t j |
� | S(/ u
Provides file.managed-like functionality (templating, etc.) for a pre-made
crontab file, to be assigned to a given user.
name
The source file to be used as the crontab. This source file can be
hosted on either the salt master server, or on an HTTP or FTP server.
For files hosted on the salt file server, if the file is located on
the master in the directory named spam, and is called eggs, the source
string is ``salt://spam/eggs``
If the file is hosted on a HTTP or FTP server then the source_hash
argument is also required
source_hash
This can be either a file which contains a source hash string for
the source, or a source hash string. The source hash string is the
hash algorithm followed by the hash of the file:
``md5=e138491e9d5b97023cea823fe17bac22``
source_hash_name
When ``source_hash`` refers to a hash file, Salt will try to find the
correct hash by matching the filename/URI associated with that hash. By
default, Salt will look for the filename being managed. When managing a
file at path ``/tmp/foo.txt``, then the following line in a hash file
would match:
.. code-block:: text
acbd18db4cc2f85cedef654fccc4a4d8 foo.txt
However, sometimes a hash file will include multiple similar paths:
.. code-block:: text
37b51d194a7513e45b56f6524f2d51f2 ./dir1/foo.txt
acbd18db4cc2f85cedef654fccc4a4d8 ./dir2/foo.txt
73feffa4b7f6bb68e44cf984c85f6e88 ./dir3/foo.txt
In cases like this, Salt may match the incorrect hash. This argument
can be used to tell Salt which filename to match, to ensure that the
correct hash is identified. For example:
.. code-block:: yaml
foo_crontab:
cron.file:
- name: https://mydomain.tld/dir2/foo.txt
- source_hash: https://mydomain.tld/hashes
- source_hash_name: ./dir2/foo.txt
.. note::
This argument must contain the full filename entry from the
checksum file, as this argument is meant to disambiguate matches
for multiple files that have the same basename. So, in the
example above, simply using ``foo.txt`` would not match.
.. versionadded:: 2016.3.5
user
The user to whom the crontab should be assigned. This defaults to
root.
template
If this setting is applied then the named templating engine will be
used to render the downloaded file. Currently, jinja and mako are
supported.
context
Overrides default context variables passed to the template.
replace
If the crontab should be replaced, if False then this command will
be ignored if a crontab exists for the specified user. Default is True.
defaults
Default context passed to the template.
backup
Overrides the default backup mode for the user's crontab.
u 0600u user.infou groupsi u changesu% Could not identify group for user {0}u commentu nameu resultu w+u
cron.raw_cronu
u {0}
Nu u/ User {0} already has a crontab. No changes madeu testu file.check_managedR t sourcet source_hasht source_hash_nameR R$ t modet attrst templatet contextt defaultst saltenvu file.source_listu file.get_managedt skip_verifyu Unable to manage file: {0}u file.manage_filet sfnR* t
source_sumt backupu diffu cron.write_cron_file_verboseu retcodeu Crontab for user {0} was updatedu1 Unable to update user {0} crontab {1}. Error: {2}u stderru, Crontab for user {0} is in the correct state( R t ExceptionR) R t saltt utilst filest mkstempt fopent endswitht writet stringutilst to_strR t ost statt st_sizet unlinkR( t __env__R
( R R1 R2 R R5 R6 t replaceR7 R< R. R3 R$ R* t cron_patht fp_t raw_cronR0 t fcmR: R; R t exct cron_ret( ( s4 /usr/lib/python2.7/site-packages/salt/states/cron.pyt file� s� \
"
c C@ s� i i d 6d d 6| d 6t d 6} t d r� t | | d | �} d | d <| d k rm d j | � | d <nN | d
k r� t | d <d j | � | d <n" | d k r� d
j | � | d <n | St d | | d | �} | d
k r� d j | � | d <| S| d k r2d j | | � | d <i | | 6| d <| S| d k rfd j | � | d <i | | 6| d <| Sd j | | | � | d <t | d <| S( uv
Verifies that the specified environment variable is present in the crontab
for the specified user.
name
The name of the environment variable to set in the user crontab
user
The name of the user whose crontab needs to be modified, defaults to
the root user
value
The value to set for the given environment variable
u changesu u commentu nameu resultu testR u absentu Cron env {0} is set to be addedu presentu Cron env {0} already presentu updateu! Cron env {0} is set to be updatedu cron.set_envu newu# Cron env {0} added to {1}'s crontabu updatedu Cron env {0} updatedu: Cron env {0} for user {1} failed to commit with error
{2}N( R R( R! R
R) R R ( R R R R* R+ R, ( ( s4 /usr/lib/python2.7/site-packages/salt/states/cron.pyt env_present� s>
c C@ sC | j � } i | d 6t d 6i d 6d d 6} t d r� t | | � } d | d <| d k r} t | d <d j | � | d <n. | d k s� | d
k r� d j | � | d <n | St d | | � } | d k r� d
j | � | d <| S| d k r d j | | � | d <i | | 6| d <| Sd j | | | � | d <t | d <| S( u4
Verifies that the specified environment variable is absent from the crontab
for the specified user
name
The name of the environment variable to remove from the user crontab
user
The name of the user whose crontab needs to be modified, defaults to
the root user
u nameu resultu changesu u commentu testu absentu Cron env {0} is absentu presentu updateu! Cron env {0} is set to be removedu cron.rm_envu Cron env {0} already absentu removedu' Cron env {0} removed from {1}'s crontabu9 Cron env {0} for user {1} failed to commit with error {2}N( R' R R( R! R
R) R R ( R R R* R+ R, ( ( s4 /usr/lib/python2.7/site-packages/salt/states/cron.pyt
env_absent� s6
( t __doc__t
__future__R R R RG t salt.utils.filesR> t salt.modules.cronR R t salt.extR R R
R R! R& R R- R/ R RS RT RU ( ( ( s4 /usr/lib/python2.7/site-packages/salt/states/cron.pyt <module>� sR 0 x ? � 4
Mini Shell