The Scheduler's functionality includes running scheduled tasks at a specified time or on a specific event, managing and launching tasks with predefined configuration and properties and more. Task configuration and properties can be used to influence launch dates and times, but also to expand the application of tasks by introducing the use of custom profiles during task execution.

The ‘scheduler_tasks’ option is commented by default, causing the default scheduler configuration to be applied. In the ESETS configuration file all parameters and tasks are semicolon-separated. Any other semicolons (and backslashes) must be backslash escaped. Each task has 6 parameters and the syntax is as follows:

id – Unique number.

name – Task description.

flags – Special flags to disable the specified scheduler task can be set here.

failstart – Instructs what to do if task could not be run on scheduled date.

datespec – A regular date specification with 6 (crontab like year-extended) fields, recurrent date or an event name option.

command – Can be an absolute path to a command followed by its arguments or a special command name with the ‘@’ prefix (e.g. anti-virus update: @update).

#scheduler_tasks = "id;name;flags;failstart;datespec;command;id2;name2;...";

The following event names can be used in place of the datespec option:

start – Daemon startup.

startonce – Daemon startup but at most once a day.

engine – Successful engine update.

login – Web interface logon startup.

threat – Threat detected.

notscanned – Not scanned email or file.

licexp – 30 days before license expiration.

To display the current scheduler configuration, use the Web interface or run the following command:

cat @ETCDIR@/esets.cfg | grep scheduler_tasks

For a full description of Scheduler and its parameters refer to the Scheduler section of the esets_daemon(8) man page.