If the application is being used in standard mode, you can configure the run schedule for the following types of tasks: ODS, Update, Rollback, ODFIM, ContainerScan, and InventoryScan.
If the application is used in Light Agent mode to protect virtual environments, you can configure the run schedule for the following types of tasks: ODS, ODFIM, ContainerScan, and InventoryScan.
You can output the current values of the settings for the task run schedule to the console or to a configuration file.
To output the current settings for the task run schedule to the console, execute the following command:
kesl-control --get-schedule <
task ID/name
> [--json]
where:
<
task ID/name
>
is the ID assigned to the task at the time of its creation, or the name of the task in the command line.--json
is specified to output the settings in JSON format. If the --json
key is not specified, the settings will be imported in the INI format. To output the current settings for the task run schedule to a configuration file, execute the following command:
kesl-control --get-schedule <
task ID/name
> --file <
path to configuration file
> [--json]
where:
<
task ID/name
>
is the ID assigned to the task at the time of its creation, or the name of the task in the command line.--file <
path to configuration file
>
is the path to the configuration file in which the settings for the task run schedule will be output. If you specify the name of a file without its path, the file will be created in the current directory. If a file already exists in the specified path, it will be overwritten. If the specified directory does not exist, the configuration file will not be created.--json
is specified to output the settings in JSON format. If the --json
key is not specified, the settings will be imported in the INI format. Examples: Save the update task settings to a file named update_schedule.ini and save the created file in the current directory:
Display the update task schedule in the console:
|
You can edit the settings for the task run schedule in the following ways:
<
setting name
>=<
setting value
>
.To edit the values of the settings for task run schedule using a configuration file, perform the following actions:
kesl-control --get-schedule
.kesl-control --set-schedule <
task ID/name
> --file <
path to configuration file
> [--json]
where:
<
task ID/name
>
is the ID assigned to the task at the time of its creation, or the name of the task in the command line.
--file <
configuration file path
>
– full path to the configuration file from which the task schedule settings will be imported.
--json
: specify this key if you are importing settings from a configuration file in JSON format. If the --json
key is not specified, the application attempts to import from an INI file. If the import fails, an error is displayed.
All values of the settings for the task run schedule defined in the file will be imported into the application.
Example: Import the schedule settings from the configuration file named /home/test/on_demand_schedule.ini into the task with ID=2:
|
To edit the individual values of the settings for the task run schedule using the command line, execute the following command:
kesl-control --set-schedule <
task ID/name
> <
setting name
>=<
setting value
> [<
setting name
>=<
setting value
>]
where:
<
task ID/name
>
is the ID assigned to the task at the time of its creation, or the name of the task in the command line.<
setting name
>=<
setting value
>
is the name and value of one of the settings for the task schedule.The values of the specified settings for the task run schedule are modified.
Examples: To schedule the task to start every ten hours, specify the following settings:
To schedule the task to start every ten minutes, specify the following settings:
To schedule the task to start on the 15th of every month, specify the following settings:
To schedule the task to start on every Tuesday, specify the following settings:
To schedule the task to start every 11 days, specify the following settings:
|