You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+4-2Lines changed: 4 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -54,13 +54,15 @@ The chef_client_scheduled_task resource setups up Chef Infra Client to run as a
54
54
-`frequency_modifier` Numeric value to go with the scheduled task frequency - default: '30'
55
55
-`start_time` The start time for the task in HH:mm format (ex: 14:00). If the `frequency` is `minute` default start time will be `Time.now` plus the `frequency_modifier` number of minutes.
56
56
-`start_date` - The start date for the task in `m:d:Y` format (ex: 12/17/2017). nil by default and isn't necessary if you're running a regular interval.
57
-
-`splay` - A random number of seconds between 0 and X to add to interval. default: '300'
57
+
-`splay` - A random number of seconds between 0 and X to add to interval. Note splay is applied differently when use_consistent_splay is set to true. default: '300'
58
58
-`config_directory` - The path to the Chef config directory. default: 'C:/chef'
59
59
-`log_file_name` - The name of the log file. default: 'client.log'
60
60
-`log_directory` - The path to the Chef log directory. default: 'CONFIG_DIRECTORY/log'
61
61
-`chef_binary_path` - The path to the chef-client binary. default: 'C:/opscode/chef/bin/chef-client'
62
62
-`daemon_options` - An optional array of extra options to pass to the chef-client
63
63
-`task_name` - The name of the scheduled task. This allows for multiple chef_client_scheduled_task resources when it is used directly like in a wrapper cookbook. default: 'chef-client'
64
+
-`use_consistent_splay` - Indicates that the randomly computed splay should remain consistent for a given node, similar to how it functions in cron resource. default: false
65
+
-`snap_time_to_frequency` - Indicates that the start day and time for the task should be snapped to start at the next frequency cycle after the previous top of the hour. For example if the current time is 14:07 and the frequency_modifier is 30, the next task start time should be 14:30. Only applicable when frequency = 'minute'. default: false
64
66
65
67
### chef_client_cron
66
68
@@ -244,7 +246,7 @@ Use this recipe to run chef-client as a cron job rather than as a service. The c
244
246
245
247
### task
246
248
247
-
Use this recipe to run chef-client on Windows nodes as a scheduled task. Without modifying attributes the scheduled task will run 30 minutes after the recipe runs, with each chef run rescheduling the run 30 minutes in the future. By default the job runs as the system user. The time period between runs can be modified with the `default['chef_client']['task']['frequency_modifier']` attribute and the user can be changed with the `default['chef_client']['task']['user']` and `default['chef_client']['task']['password']` attributes.
249
+
Use this recipe to run chef-client on Windows nodes as a scheduled task. Without modifying attributes the scheduled task will run 30 minutes after the recipe runs, with each chef run rescheduling the run 30 minutes in the future. By default the job runs as the system user. The time period between runs can be modified with the `default['chef_client']['task']['frequency_modifier']` attribute and the user can be changed with the `default['chef_client']['task']['user']` and `default['chef_client']['task']['password']` attributes. For a scheduled task that behaves more like the chef-client cron job, the snap_time_to_frequency and use_consistent_splay properties can be set to true.
0 commit comments