|
The drwreploader.conf Repository Loader configuration file is presented in the XML format and located in the etc subfolder of the Dr.Web Server installation folder.
To use the configuration file
•For the console utility, the path to the file must be specified in the --config switch. •For the graphical utility, the file must reside in the utility folder. If the utility is ran without configuration file, it will be created in the utility folder and will be used at next launches. Description of the Repository Loader configuration file parameters:
•<mode value="" path="" archive="" key=""> Attributes description:
Attribute
|
Description
|
Allowed values
|
value
|
Updates loading mode:
•repository—repository is downloaded in the Dr.Web Server repository format. Loaded files can be directly imported via the Control Center as the Dr.Web Server repository updates. •mirror—repository is downloaded in the GUS updates zone format. Loaded files can be placed on the updates mirror in your local network. Further, Dr.Web Servers can be configures to receive updates directly from this updates mirror containing the last version of the repository but not from the GUS servers. |
repository | mirror
|
path
|
The folder for downloading the repository.
|
–
|
archive
|
Pack downloaded repository into a zip archive automatically. This option allows to get prepared archive file for import downloaded repository archive to Dr.Web Server via the Control Center, for the Administrating → Repository Content section.
|
yes | no
|
key
|
Dr.Web license key file. Instead of a license key you can specify only MD5 hash of a license key, which you can view in the Control Center in the Administration → License Manager section.
|
–
|
•<log path="" verbosity="" rotate=""> Repository Loader log settings.
Attributes description:
Attribute
|
Description
|
Allowed values
|
path
|
Path to the log file.
|
–
|
verbosity
|
Log level of detail. TRACE3 is by default.
|
ALL, DEBUG3, DEBUG2, DEBUG1, DEBUG, TRACE3, TRACE2, TRACE1, TRACE, INFO, NOTICE, WARNING, ERROR, CRIT. The ALL and DEBUG3 values are synonyms.
|
rotate
|
Repository Loader log rotation mode in the format: <N><f>,<M><u>. Same as the Dr.Web Server log rotation.
By default, it is 10,10m, which means storing of 10 files 10 megabytes each, use compression.
|
–
|
•<update url="" proto="" cdn="" update-key="" version=""> General repository loading settings.
Attributes description:
Attribute
|
Description
|
Allowed values
|
url
|
A GUS servers folder where updates of Dr.Web products are located.
|
–
|
proto
|
The protocol type to receive updates from update servers. For all protocols, updates are downloaded according to the settings of the GUS servers list.
|
http | https | ftp | ftps | sftp | scp | file
|
cdn
|
Allow downloading repository from GUS via Content Delivery Network
|
yes | no
|
update-key
|
Path to a public key or to a folder with a public key to validate the signature of updates that are loaded from GUS. The update-key-*.upub public keys to validate updates can be found on Dr.Web Server in the etc folder.
|
–
|
version
|
The Dr.Web Server version to which the updates must be loaded.
|
–
|
▫<servers> Update servers list. GUS servers are listed in the order the utility contacts them when downloading the repository.
Contains the <server> child elements with update servers.
▫<auth user="" password=""> User credentials to authenticate on updates server, if the updates server requires authorization.
Attributes description:
Attribute
|
Description
|
user
|
User name at updates server.
|
password
|
Password at updates server.
|
▫<proxy host="" port="" user="" password="" /> Parameters for connecting to the GUS via the proxy server.
Attributes description:
Attribute
|
Description
|
host
|
The network address of the proxy server.
|
port
|
The port number of the proxy server. Default is 3128.
|
user
|
User name on the proxy server if used proxy server requests authorization.
|
password
|
Password on the proxy server if used proxy server requests authorization.
|
▫<ssl cert-mode="" cert-file=""> The type of SSL certificates that will be automatically accepted. This option is used only for secure protocols that support encrypting.
Attributes description:
Attribute
|
Description
|
Allowed values
|
cert-mode
|
Certificated to accept automatically.
|
▫any—accept all certificates, ▫valid—accept only valid certificates, ▫drweb—accept only Dr.Web certificates. ▫custom—accept user-defined certificates. |
cert-file
|
Path to the cert file.
|
–
|
▫<ssh mode="" pubkey="" prikey=""> The type of the authorization on the update server when accessing by SCP/SFTP.
Attributes description:
Attribute
|
Description
|
Allowed values
|
mode
|
Authorization type.
|
▫pwd—authorization using a password. A password is set in the <auth /> tag. ▫pubkey—authorization using a public key. A public key is set in the pubkey attribute or extracted from the private key specified in the prikey. |
pubkey
|
Public SSH key
|
–
|
prikey
|
Private SSH key
|
–
|
•<products> Loading products settings.
▫<product name="" update=""> Each product settings separately.
Attributes description:
Attribute
|
Description
|
Allowed values
|
name
|
Product name.
|
•05-drwmeta—Dr.Web Server security data, •10-drwbases—virus databases, •10-drwgatedb—SpIDer Gate bases, •10-drwspamdb—Anti-spam bases, •10-drwupgrade—Dr.Web Updater, •15-drwhashdb—known hashes of threats, •20-drwagent—Dr.Web Agent for Windows, •20-drwandroid11—Dr.Web for Android databases, •20-drwcs—Dr.Web Server, •20-drwunix—Dr.Web Agent for UNIX, •20-drwcsdoc—documentation, •40-drwproxy—Dr.Web Proxy Server, •70-drwextra—Dr.Web enterprise products, •70-drwutils—Dr.Web administrative utilities, •80-drwnews—Doctor Web News. |
update
|
Enable this product downloading.
|
yes | no
|
•<schedule> The schedule to receive updates periodically. At this, you do not have to launch the utility manually, the repository downloading performed automatically according to the specified time slots.
▫<job period="" enabled="" min="" hour="" day="" /> Settings of scheduled loading execution.
Attribute
|
Description
|
Allowed values
|
period
|
Periodicity for loading task execution.
|
•every_n_min—every N minutes, •hourly—every hour, •daily—every day, •weekly—every week. |
enabled
|
Downloading task is enabled.
|
yes | no
|
min
|
Minute to execute the task.
|
integers from 0 to 59
|
hour
|
Hour to execute the task. Relevant for daily and weekly.
|
integers from 0 to 23
|
day
|
Day to execute the task. Relevant for weekly.
|
•mon—Monday, •tue—Tuesday, •wed—Wednesday, •thu—Thursday, •fri—Friday, •sat—Saturday, •sun—Sunday. |
|