F2. Products configuration files

Top  Previous  Next

.description

The .description file sets a product name. If the file is absent, the name of the respective folder of the product is used as the product name.

For Example:

Dr.Web Server

.sync-off

The file disables the product update. Content is irrelevant.

Files of Exclusions in Updating the Server Repository from the GUS

.sync-only

The .sync-only file contains the regular expressions that define the list of repository files which will be synchronized during update of the repository from the GUS. Repository files not specified in the .sync-only, will not be synchronized. If the .sync-only file is absent, all repository files will be synchronized except those files which are excepted according to the settings in the .sync-ignore file.

.sync-ignore

The .sync-ignore file contains the regular expressions that define the list of repository files which will be excluded from synchronization during update of the repository from the GUS.

Example of the file with exceptions:

^windows-nt-x64/

^windows-nt/

^windows/

The Order of Use of Configuration Files

If the .sync-only and .sync-ignore files are present for the product, the following scheme of actions is used:

1.The .sync-only is applied first. Files not listed in the .sync-only, are not handled.

2.To the rest of files, the .sync-ignore is applied.

Files of Exclusions in Updating the Agents from the Server

.state-only

The .state-only file contains the regular expressions that define the list of repository files which will be synchronized during update of the Agents from the Server. Repository files not specified in the .state-only, will not be synchronized. If the .state-only file is absent, all repository files will be synchronized except those files which are excepted according to the settings in the .state-ignore file.

.state-ignore

The .state-ignore file contains the regular expressions that define the list of repository files which will be excluded from synchronization during update of the Agents from the Server.

For Example:

German, Polish and Spanish interface languages should not be received (others—will be received),

no components designed for Windows OS 64-bit should be received.

;^common/ru-.*\.dwl$ this will be updated

^common/de-.*\.dwl$

^common/pl-.*\.dwl$

^common/es-.*\.dwl$

^win/de-.*

^win/pl-.*

^windows-nt-x64\.*

The order of using .state-only and .state-ignore is the same as for the .sync-only and .sync-ignore.

Notification Sending Configuration

The files of the notify group allow to configure the notification system on successful update of the separate products.

These settings are refer the Product has been updated notification only. To all other notification types, exceptions are not applied.

The setting of the notification system is described in Administrator Manual, p. Setting Notifications.

.notify-only

The .notify-only file contains the list of repository files on changing of which the notification will be sent.

.notify-ignore

The .notify-ignore file contains the list of repository files on changing of which the notification will not be sent.

The Order of Use of Configuration Files

If the .notify-only and .notify-ignore files are present for the product, the following scheme of actions is used:

1.At product update, files updates from the GUS, are compared with exclusions list.

2.Files included into the .notify-ignore list, are excluded first.

3.From the rest of files, whose are excluded which are not in the .notify-only list.

4.If files not excluded on the previous steps are remained, notifications will be sent.

If the .notify-only and .notify-ignore files are absent, notifications will be always sent (if they are enabled on the Notifications configuration page in the Control Center).

For Example:

If in the .notify-ignore file, the ^.vdb.lzma$ exception is set, and only virus databases are updated, notification will not be sent. If the drweb32.dll engine is updated with the databases, when notification will be sent.

Freeze Settings

.delay-config

The .delay-config file contains settings to disable switching the product to the new revision. Repository continues distributing the previous revision, and synchronization is no longer performed (the state of the product become "frozen"). If administrator decides that received revision is adequate for distributing, administrator must enable its distribution in the Control Center (see Administrator Manual, p. Administration of Dr.Web Server Repository).

The file contains two not case sensitive parameters which are separated by a semicolon.

File format:

Delay [ON|OFF]; UseFilter [YES|NO]

Parameter

Possible values

Description

Delay

ON|OFF

ON—freeze of product updates is enabled.

OFF—freeze of product updates is disabled.

UseFilter

YES|NO

Yes—freeze updates only if updates files match the exceptions list in the .delay-only file.

No—freeze updates in any case.

For Example:

Delay ON; UseFilter NO

.delay-only

The .delay-only file contains the list of files, changing of which disables the switching the product on a new revision. The list of files is set in a regular expressions format.

If the file from the repository update meets the specified masks and the UseFilter setting in the .sync-only file if enabled, when revision will be frozen.

.rev-to-keep

The .rev-to-keep file contains the number of stored product revisions.

For Example:

3