Interface and Dr.Web Server Management
Dr.Web Server has no interface. As a rule, Dr.Web Server can be managed via Dr.Web Security Control Center, which acts as an interface for Dr.Web Server.
Dr.Web Server installation folder has the following structure:
/opt/drwcs/ for Linux OS and /usr/local/drwcs for FreeBSD OS:
•bin—Dr.Web Server executable files.
•doc—license agreements files.
•ds-modules—unpacked script modules.
•fonts—fonts for PDF documents.
•lib—libraries set for the Dr.Web Server operation.
•vfs—packed script modules and language packages.
•webmin—Control Center elements.
•websockets—web sockets scripts.
/var/opt/drwcs/ for Linux OS and /var/drwcs for FreeBSD OS:
•backup—backups of DB and other critical data.
•coredump—Dr.Web Server crash dumps. Created at dumps appearance.
•etc—general configuration files of anti-virus network components.
•extensions—scripts of user hooks meant to automate the performance of certain tasks.
•installers-cache—cache to store Dr.Web Agent personal and group installation packages when stations are created via the Control Center. Created at installation packages creation.
•file-cache—file cache.
•log—Dr.Web Server log files.
•plugins—temporary plug-ins objects.
•objects—Control Center objects cache.
•reports—temporary folder for generating and storing reports. Created when necessary.
•repository—repository folder to store actual updates of virus bases, anti-virus packages files and anti-virus network components. The folder contains subfolders for the program components software which include subfolders for their versions depending on the OS. The folder should be accessible for writing to the user under which Dr.Web Server is launched (the drwcs as a rule).
•run—Dr.Web Server process ID.
•sessions—Control Center sessions.
•tmp—temporary files.
•twin-cache—unpacked virus bases for backward compatibility with previous versions of Dr.Web Agents. Also, can contain other unpacked repository files, e.g., the Dr.Web Agent installer.
•upload—folder to download temporary files which are specified via the Control Center. Created at large files downloading.
/etc/opt/drweb.com/ for Linux OS and /usr/local/etc/drweb.com for FreeBSD OS:
•software/drweb-esuite.remove—script to remove Dr.Web Server.
•also additional files and folders are possible.
/usr/local/etc/rc.d/ for FreeBSD OS:
•drwcsd—script to start and stop Dr.Web Server.
/var/tmp/drwcs—backup after the Dr.Web Server removal.
General Configuration Files
File |
Description |
Default folder |
|---|---|---|
agent.key (name may vary) |
Dr.Web Agent license key |
•for Linux OS: •for FreeBSD OS: |
certificate.pem |
SSL certificate |
|
common.conf |
configuration file (for some of Unix-like OS) |
|
database.conf |
database settings template with default parameters |
|
download.conf |
network settings for generating of the Dr.Web Agent installation packages |
|
drwcsd.conf (name may vary) |
Dr.Web Server configuration file |
|
drwcsd.conf.distr |
Dr.Web Server configuration file template with default parameters |
|
drwcsd.pri |
private encryption key |
|
enterprise.key (name may vary) |
Dr.Web Server license key file. The file is saved if it presented after the upgrade from the previous versions. For the new Dr.Web Server 13.0 installation, the file is absent |
|
frontdoor.conf |
configuration file for the Dr.Web Server remote diagnostic utility |
|
http-alerter-certs.pem |
certificates for verification the apple-notify.drweb.com host for sending push notifications |
|
private-key.pem |
RSA private key |
|
yalocator.apikey |
API key for the Yandex.Locator extension |
|
webmin.conf |
Control Center configuration file |
|
auth-ldap.conf |
configuration file for administrators external authorization via LDAP |
|
auth-ldap-rfc4515.conf |
configuration file for administrators external authorization via LDAP using the simplified scheme |
|
auth-pam.conf |
configuration file for administrators external authorization via PAM |
|
auth-radius.conf |
configuration file for administrators external authorization via RADIUS |
|
database.sqlite |
embedded database |
•for Linux OS: •for FreeBSD OS: |
*.pub |
public encryption key |
Administration → Encryption keys in the Control Center |
By default, Dr.Web Server automatically starts after installation and every time after restarting the operating system.
Also you can start or start, restart or stop Dr.Web Server by one of the following ways:
•Stop and restart via the Control Center:
▫In the Administration section, use buttons: 
to restart, 
to stop.
•Using the corresponding console command (see also the Appendices document, G3. Dr.Web Server):
▫Start:
▪for FreeBSD OS:
# /usr/local/etc/rc.d/drwcsd start
▪for Linux OS:
# /etc/init.d/drwcsd start
▫Restart:
▪for FreeBSD OS:
# /usr/local/etc/rc.d/drwcsd restart
▪for Linux OS:
# /etc/init.d/drwcsd restart
▫Stop:
▪for FreeBSD OS:
# /usr/local/etc/rc.d/drwcsd stop
▪For Linux OS:
# /etc/init.d/drwcsd stop
|
Please note, if you need Dr.Web Server to read environment variables, the service must be rebooted via the console command. |
