Name: cron
Owner: LinuxONE and Linux on z Systems Open-source Team
Description: Development repository for Chef Cookbook cron
Created: 2016-04-12 16:56:10.0
Updated: 2016-04-12 16:56:11.0
Pushed: 2016-04-13 04:42:26.0
Homepage: https://supermarket.chef.io/cookbooks/cron
Size: 154
Language: Ruby
GitHub Committers
User | Most Recent Commit | # Commits |
---|
Other Committers
User | Most Recent Commit | # Commits |
---|
Installs the cron package and starts the crond service.
cron_d
The cron_d
LWRP can be used to manage files in /etc/cron.d
. It supports the same interface as Chef's built-in cron
resource:
_d 'daily-usage-report' do
nute 0
ur 23
mmand '/srv/app/scripts/daily_report'
er 'appuser'
Note: FreeBSD does not support cron.d functionality, so it is emulated. cron fragments are created in /etc/cron.d, then they are concatenated together into /etc/crontab. FreeBSD puts some core OS functionality into /etc/crontab, so the original file is copied to /etc/crontab.os_source, and included in the concatenation.
Note: This LWRP does not function on Solaris platforms because they do not support running jobs stored in /etc/cron.d. Any Solaris users are welcome to test the emulate_cron.d functionation that was implemented for FreeBSD. See defaults/attributes.rb for more information.
minute
, hour
, day
, month
, weekday
- schedule your cron job. These correspond exactly to their equivalents in the crontab file. All default to “*“.predefined_value
- schedule your cron job with one of the special predefined value instead of * pattern. This correspond to "@reboot"
, "@yearly"
, "@annually"
, "@monthly"
, "@weekly"
, "@daily"
, "@midnight"
or "@hourly"
.command
- the command to run. Required.user
- the user to run as. Defaults to “root”.mailto
, path
, home
, shell
- set the corresponding environment variables in the cron.d file. No default.environment
- a Hash containing additional arbitrary environment variables under which the cron job will be run (similar to the shell
LWRP). No default.mode
- the octal mode of the generated crontab file. Defaults to 0644
.cron_manage
The cron_manage
definition can be used to manage the /etc/cron.allow
and /etc/cron.deny
files. Incude this cookbook as dependency to your cookbook and execute the definition as:
The following will add the user mike to the /etc/cron.allow
file:
_manage 'mike' do
er 'mike'
tion :allow
The following will add the user john to the /etc/cron.deny
file:
_manage 'john' do
er 'john' #optional, resource name will be used if not specified.
tion :deny #optional, deny is the default
user
- username that you want to control (optional).action
- :allow
or :deny
. :deny is the default.right 2010-2015, Chef Software, Inc.
nsed under the Apache License, Version 2.0 (the "License");
may not use this file except in compliance with the License.
may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
ss required by applicable law or agreed to in writing, software
ributed under the License is distributed on an "AS IS" BASIS,
OUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
the License for the specific language governing permissions and
tations under the License.