.description
The .description file specifies the 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 |
..languages
The ..languages file contains a list of language codes for which the update is configured. If the file is missing or empty, no update is configured for any languages, so it will not be performed.
..platforms
The ..platforms file contains the full platform codes used in the product for which the update is configured. If the file is missing or empty, no update is configured for any platforms, so it will not be performed.
..formats
The ..formats file contains the file formats that are configured to update, for example, document formats (html, pdf). If the file is missing or empty, no update is configured for any formats, so it will not be performed.
..items
The ..items file determines which administrative utilities or enterprise products are updated. If the file is missing or empty, no update is configured for any utilities or products, so it will not be performed.
.sync-off
The file disables product updates. Its contents are irrelevant.
.deleted
The .deleted file marks the product as removed. All revisions from it will be deleted, synchronization with the GUS is disabled.
Exclusion files for updating Dr.Web Server Repository from GUS
.sync-only
The .sync-only file contains regular expressions that define the list of repository files that will be synchronized during a repository update from the GUS. Repository files not specified in the .sync-only file will not be synchronized. If the .sync-only file is absent, all repository files will be synchronized except for files excluded according to the settings in the .sync-ignore file.
.sync-ignore
The .sync-ignore file contains regular expressions that define the list of repository files that will be excluded from synchronization during a repository update from the GUS.
Example of the exception file:
^windows-nt-x64/ ^windows-nt/ ^windows/ |
Order of use of configuration files
If the .sync-only and .sync-ignore files are present for a product, the following procedure is used:
1..sync-only is applied first. Files not listed in .sync-only are not handled.
2..sync-ignore is applied to the rest of the files.
Exclusion files for updating Dr.Web Agents from Dr.Web Server
.state-only
The .state-only file contains regular expressions that define the list of repository files that will be synchronized when Dr.Web Agents are updated from Dr.Web Server. Repository files not specified in the .state-only file will not be synchronized. If the .state-only file is absent, all repository files will be synchronized except for files excluded according to the settings in the .state-ignore file.
.state-ignore
The .state-ignore file contains regular expressions that define the list of repository files that will be excluded from synchronization when Dr.Web Agents are updated from Dr.Web Server.
For example:
•do not receive German, Chinese, and Spanish interface languages (others will be received),
•do not receive any components designed for 64-bit Windows.
;^common/ru-.*\.dwl$ this will be updated ^common/de-.*\.dwl$ ^common/cn-.*\.dwl$ ^common/es-.*\.dwl$ ^win/de-.* ^win/cn-.* ^windows-nt-x64\.* |
The order of using .state-only and .state-ignore is the same as for the .sync-only and .sync-ignore files.
Notification sending configuration
The files of the notify group configure notifications on a successful update of repository products.
|
The following settings affect the Product has been updated notification only. The exceptions are not applied to other notification types. Configuration of the notification system is described in the Administrator Manual, the Setting Notifications section. |
.notify-only
The .notify-only file contains a list of repository files whose modification triggers a notification.
.notify-ignore
The .notify-ignore file contains a list of repository files whose modification does not trigger a notification.
Order of use of configuration files
If the .sync-only and .sync-ignore files are present for a product, the following procedure is used:
1.When a product is being updated, files updated from the GUS are compared with the list of exclusions.
2.Files on the .notify-ignore list are excluded first.
3.Files not on the .notify-only list are excluded from the rest of the files.
4.If any files not excluded in the previous steps remain, notifications are sent.
If the .notify-only and .notify-ignore files are absent, notifications are always sent (if they are enabled on the Notifications configuration page in the Control Center).
For example:
If the ^.vdb.lzma$ exception is set in the .notify-ignore file and only virus databases are updated, a notification is not sent. If the drweb32.dll engine file is updated alongside the virus databases, a notification will be sent.
Freeze settings
.delay-config
The .delay-config file contains settings to disable switching the product to a new revision. The repository continues to distribute the previous revision, and synchronization is no longer performed (the state of the product is "frozen"). If the administrator decides that a new revision is fit to be distributed, the administrator must enable its distribution in the Control Center (see the Administrator Manual, Administration of Dr.Web Server Repository).
The file contains two case insensitive parameters which are separated by a semicolon.
File format:
Delay [ON|OFF|APPROVAL]; UseFilter [YES|NO]
Parameter |
Possible values |
Description |
|---|---|---|
Delay |
ON|OFF|APPROVAL |
•ON—product update freeze is enabled. •OFF—product update freeze is disabled. •APPROVAL—product update freeze is enabled until administrator approval. |
UseFilter |
YES|NO |
•Yes—freeze updates only if update files match the exception 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 a list of files whose modification disables switching the product to a new revision. The list of files is set in the regular expression format.
If a file from a repository update matches a specified mask and the UseFilter setting in the .sync-only file is enabled, the revision is frozen.
.rev-to-keep
The .rev-to-keep file contains the number of product revisions to be stored.
For example:
3 |
.on-demand
The presence of the .on-demand file means that on-demand synchronization of the product is enabled, i.e. if there are customers requesting this product.
.is-sync-off-in
The presence of the .is-sync-off-in file means that receiving product updates via inter-server communications is disabled.
.is-sync-off-out
The presence of the .is-sync-off-out file means that the distribution of product updates via inter-server communications is disabled.
.no-platform
The presence of the .no-platform file means that the top-level directories in the product revision are not considered platforms, that is, the revision applies to any platform.