The Description Instruction
The description instruction sets a product name which is displayed in the Dr.Web Control Center. If this instruction is unavailable, the name of the respective folder of the product is used as the product name.
Example:
description '"Dr.Web® Enterprise Agent" |
The sync-with Instruction
The sync-with instruction sets the list of HTTP servers and HTTP-proxy servers for updating. The name parameter sets the domain name or the IP address. The :port construction may be absent, in this case, by default, 80 will be regarded the port number for the HTTP server and 3128 for the proxy server.
The servers in the list are polled consequently, once the updating is successful, the polling procedure terminates.
|
The current Dr.Web Enterprise Security Suite version supports only base HTTP authentication, proxy-HTTP authentication and RADIUS authentication.
Constant HTTP redirects (code 301) are cached in memory till server reboot. |
Example:
sync-with{ http{ esuite.msk3.drweb.com /update } http{ esuite.msk4.drweb.com /update } http{ esuite.msk.drweb.com /update } http{ esuite.us.drweb.com /update } http{ esuite.jp.drweb.com /update } } |
If using the proxy server
sync-with{ http-proxy{ 10.3.0.74 auth user:pass http{ esuite.msk7.drweb.com /update } } http-proxy{ 10.3.0.74 auth user:pass http{ esuite.jp.drweb.com /update } } http-proxy{ 10.3.0.74 auth user:pass http{ esuite.msk5.drweb.com /update } } http-proxy{ 10.3.0.74 auth user:pass http{ esuite.msk6.drweb.com /update } } http-proxy{ 10.3.0.74 auth user:pass http{ esuite.msk.drweb.com /update } } http-proxy{ 10.3.0.74 auth user:pass http{ esuite.us1.drweb.com /update } } http-proxy{ 10.3.0.74 auth user:pass http{ esuite.msk3.drweb.com /update } } http-proxy{ 10.3.0.74 auth user:pass http{ esuite.msk4.drweb.com /update } } http-proxy{ 10.3.0.74 auth user:pass http{ esuite.us.drweb.com /update } } http-proxy{ 10.3.0.74 auth user:pass http{ esuite.fr1.drweb.com /update } } } |
where:
◆10.3.0.74 - IP-address of the proxy server;
◆user - name of the user to access the proxy server (may be absent, if the proxy do not require authentication);
◆pass - password to access the proxy server (may be absent, if the proxy do not require authentication).
The sync-only Instruction
The sync-only instruction explicitly specifies the sets of filenames (specified both by regular expressions in a simple form as shown in this section, and in full form qr{}, as shown in p. Launching and Terminating Anti-Virus Scanning on Workstations) which are subject to synchronization. If the instruction is absent, by default, the whole content of the folder will be synchronized (excluding files whose names begin with a period).
Example:
sync-only{^common/drw.*vdb$} |
instructs to update only virus databases.
The sync-ignore Instruction
The sync-ignore instruction explicitly specifies the set of files, which are not subject to synchronization.
|
If some files have been locally added to a product (which were not present in the original set) and the sync-only instruction is not used, the added files should be listed in sync-ignore, otherwise they will be deleted during synchronization. |
The sync-delay Instruction
The sync-delay instruction sets the list of files which, if changed, disable the product transition to a new revision. The repository continues to distribute the previous revision, and it is not synchronized (the state of product is "frozen"). If a user finds this revision acceptable for distribution, he must edit the .id status file and restart the Server (read Appendix F3. .id Files).
Examples:
◆The automatic distribution of new revisions is disabled:
sync-delay{ .* } ; no automatic distribution, I will test everything myself |
◆The automatic distribution of revisions where the executable files are updated is disabled:
sync-delay{ .*\.exe$ .*\.dll$ } |
The state-only and state-ignore Instructions
The state-only and state-ignore instructions set (limit) the list of files for distribution.
Example:
For Enterprise Agent:
◆german, polish and spanish interface languages should not be received (others - will be received),
◆no components designed for Windows 98 OS, Windows Me OS should be received.
sync-ignore{ ; As soon as the listed files are in the ; repository, they are to be propagated. ; Therefore, they should be deleted or ; listed in state-ignore{ } or full ; synchronization in this ; configuration should be made ;^common/ru-.*\.dwl$ we need it ^common/de-.*\.dwl$ ^common/pl-.*\.dwl$ ^common/es-.*\.dwl$ ^win/de-.* ^win/pl-.* ^win-9x\.* } |
The Instructions of the notify Group
The instructions of the notify group allow to set up the notification system for separate products (the setting of the notification system is described in p. Setting Alerts).
The repository generates the following types of notifications:
◆update — when a product is successfully updated,
◆delay — when a transaction is frozen,
◆flushfail — when a flush error occurs,
◆loadfail — when a load error occurs.
By default, all the types are allowed.
The notify-off instruction allows to disable certain types of notifications for the given product.
The notify-ignore and notify-only instructions allow to limit or specify explicitly the list of files, for which, if changed, the notification of the update type is sent.
|
If at least two of the sync-only, sync-ignore or sync-delay instructions are present in a file, the following rule is used: ◆sync-only is applied first. Files not specified in this instruction (if any), are not processed, ◆sync-ignore is applied to the rest of files, ◆sync-delay is applied only to the remaining files (after the two previous items have been applied). |
The same rule is applied to the application order of state-only and state-ignore.