Installation manual

ManualsBrandsESET ManualsPrint & ScanGATEWAY SECURITY - FOR LINUX BSD AND SOLARIS

[dac]

agent_enabled = yes

event_mask = "open"

ctl_incl = "/home"

action_av = "scan"

user_config = "esets_dac_spec.cfg"

Once the ‘user_config’ file parameter is specified within the [dac] section, the ‘esets_dac_spec.cfg’ file must be created in the ESETS

configuration directory. Finally, add the desired scanning rules.

[username]

action_av = "reject"

At the top of the special section, enter the username to which the individual rules will be applied. This configuration will allow

all other users attempting to access the file-system to be processed normally. i.e., all file system objects accessed by other users

will be scanned for infiltrations, except for the user ‘username’, whose access will be rejected (blocked).

7.3 Samples Submission System

The Samples submission system is an intelligent ThreatSense.Net technology that collects infected objects that have been

detected by advanced heuristics and delivers them to the samples submission system server. All virus samples collected by the

sample submission system will be processed by the ESET virus laboratory and if necessary, added to the ESET virus signature

database.

Note: According to our license agreement, by enabling the sample submission system you are agreeing to allow the computer

and/or platform on which the esets_daemon is installed to collect data (which may include personal information about you

and/or other users of the computer) and samples of newly detected viruses or other threats and send them to ESET virus

laboratory. This feature is disabled by default. All information collected will be used only to analyze new threats and will not be

used for any other purpose.

In order to enable sampling, the samples submission system cache must be initialized. This can be achieved by selecting

‘samples_enabled’ in the [global] section of the ESETS configuration file.

For more information on the Samples Submission System and its options, please refer to the esets_daemon(8) mane page.

7.4 Scheduler

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.

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.