Updating Procedure

Updating is performed in the following stages:

1.Dr.Web Updater reads the configuration file (drweb32.ini by default, or specified with the --ini command line argument).

2.Dr.Web Updater uses parameters from the [Updater] section of the configuration file (see the description above) as well as the following parameters: EnginePath, VirusBase, UpdatePath and PidFile.

3.Dr.Web Updater selects Dr.Web GUS server for downloading updates. The server is selected in the following way:

•Reading of the files which contain lists of update servers. The filenames are specified in the DrlFile and CustomDrlFile parameters;

•If both files are not accessible, updating process stops and terminates;

•If only one of the files is accessible, it is used regardless of the value specified for the FallbackToDrl parameter;

•If both files are accessible, Dr.Web Updater uses the file specified in the CustomDrlFile parameter;

•If it is impossible to connect to any of the servers from this file (specified in CustomDrlFile), and the FallbackToDrl value is set to Yes, Dr.Web Updater tries to establish connection with the servers from the file specified in the DrlFile parameter. If the connection fails, the updating process stops and terminates.

4.Dr.Web Updater tries to connect to servers from the selected file in random order until connection is established (Dr.Web Updater waits for the server to respond during the period specified in the Timeout parameter).

5.Dr.Web Updater requests the list of available updates from the selected Dr.Web GUS server and then requests the corresponding lzma archives. If the archives are not available on the server, the updates are downloaded as vdb files. To unpack lzma-archives, lzma utility is used. Path to the directory with the utility is specified in the LzmaDecoderPath parameter.

6.After updates are unpacked, they are saved to the corresponding directories as described in Updating.