Lists of frequently asked questions

Search:

How does the type of installation (via a universal package or directly from the repository) affect further product operation?

The selected method of initial installation affects how further updates are obtained. After installing Dr.Web anti-virus for Linux using any of the possible ways, the package manager automatically connects to the Dr.Web package repository. This can cause problems when installing the universal .run package on a station that lacks access to an external network. In this case, the solution is to temporarily disconnect from the repositories during the installation process.

If you encounter any difficulties with the repositories after installing the .run package, please contact our technical support.

Updating databases

By default, the virus databases are updated automatically if you have Internet access.

Permanent link

Updating packages and components (within a current version)

During the initial installation from the repository, the components will be automatically updated from it (provided that automatic updating is allowed and the station has access to it).

If the installation was performed from the universal .run package, the ability to get automatic updates from the repository depends on the specifics of the user's operating system. In this case, updating from Dr.Web Server actually means installing a new .run package over the existing one. The Dr.Web Enterprise Security Suite repository and the repository https://repo.drweb.com, to which the package manager is connected, are different objects with different content.

If a product installed using the .run package is not updated automatically

In this case, the zypper package manager (included in the installed Dr.Web anti-virus for Linux package) should be used to perform a manual update. If this method is not suitable for some reason, you should apply the update commands of the package manager used in your OS.

Updating using zypper, included in the product in Linux distributions, is performed by the following commands:

# /opt/drweb.com/bin/zypper refresh

# /opt/drweb.com/bin/zypper update

For FreeBSD:

# /usr/local/libexec/drweb.com/bin/zypper refresh

# /usr/local/libexec/drweb.com/bin/zypper update

At the same time, repo.drweb.com should be available from the station where the updating process is launched.

Details and examples of commands can be found in the official documentation.

Permanent link

Upgrading to a new version

If a new version of Dr.Web anti-virus for Linux is released, packages containing its components are placed in the section of the Dr.Web repository that corresponds to the new version. In this case, the package manager should be switched to the new section of the Dr.Web repository (for more information refer to "Upgrading to a new version").

Permanent link

Receiving updates on stations without Internet access

A utility for creating a local update mirror is available so that updates can be received on isolated stations. Instructions on its use and more information on this topic can be found here.

Updating the databases of a product installed directly from the repository on an isolated station

The updating process is performed as follows: updates are downloaded to a computer connected to the Internet, copied to a USB drive or network drive, and then installed on another computer that is not connected to the Internet.
The updating process is performed via the command line.

Instructions for receiving updates

On a computer connected to the Internet, run the following command:

$ drweb-ctl update --Path <path to the directory to which updates will be downloaded>

Copy the received updates to a USB drive or a network drive.
Mount a network drive or a USB drive on the computer on which you want to install updates. If you receive updates from a USB drive, you will need to run the following commands:

# mkdir /mnt/usb

# mount <path to device> /mnt/usb

Install updates using the following command:

$ drweb-ctl update --From /mnt/usb

You can also download new .rpm packages on any other PC with access to https://repo.drweb.com and then transfer them to the target station.

Permanent link

Updating the databases of a product installed from the universal .run package on an isolated station

In this case, the zypper package manager (included in the installed Dr.Web anti-virus for Linux package) should be used. If this method is not suitable for some reason, you should apply the update commands of the package manager used in your OS.

Conditions for the example shown below: there is a second station with Internet access and a .run package installed on it.

Checking the content of the repository (without updating) for Linux:

# /opt/drweb.com/bin/zypper up

For FreeBSD:

# /usr/local/libexec/drweb.com/bin/zypper up

The answer “N” to the question "Continue? [y/n/...? display all parameters] (y):" will complete the command without installing updates.

Download everything new by listing all the packages in the command (for Linux):

# /opt/drweb.com/bin/zypper download …

For FreeBSD:

# /usr/local/libexec/drweb.com/bin/zypper download ...

After that, all updates for our run package are available in the catalogue /var/opt/drweb.com/cache/zypp/packages/drweb-11.1/ (for Linux) or /var/drweb.com/cache/zypp/packages/drweb-11.1/ (for FreeBSD).

Transfer this entire directory with all the attachments to the station with the product that needs updating. The name and path to the directory on the target station are of no importance (for example /tmp/1).
Then, enter the following command (for Linux) on the isolated station:

# /opt/drweb.com/bin/rpm -Uhv /tmp/1/*

For FreeBSD:

# /usr/local/libexec/drweb.com/bin/rpm -Uhv /tmp/1/*

Permanent link

Back

Nothing found

Find out more

User
Guide

Configure
Dr.Web!

Training
courses

Video