•drwcsd restart—restart Dr.Web Server (it is executed as the stop and then start pair).
•drwcsd start—run Dr.Web Server.
•drwcsd stop—stop Dr.Web Server.
•drwcsd stat—log statistics to a file: CPU time, memory usage, etc. (for Unix-like OS—similar to send_signal WINCH or kill SIGWINCH commands).
•drwcsd modexec agent@verify-key <full_key_filename>—verify the license key file (agent.key).
•drwcsd modexec enterprise@verify-key <full_key_filename>—verify the Dr.Web Server license key file (enterprise.key). Please note that the Dr.Web Server license key file is no longer used from the version 10.
•drwcsd verifyconfig <full_config_filename>—verify the syntax of the Dr.Web Server configuration file (drwcsd.conf).
•drwcsd verifycache—verify content of the Dr.Web Server's file cache.
•drwcsd syncads—synchronize the network structure: Active Directory containers that contain computers become anti-virus network groups where workstations are placed into.
•drwcsd modexec restore@repository-server-update—restore Dr.Web Server from revision (roll back to the state of the selected revision without saving a backup copy, updating the database and configuration files). If this revision is absent in the repository, nothing will happen.
|
This action is recorded in the audit log. |
•update@repository-server-update [<revision-to>]—update Dr.Web Server. If no revision is specified to update to, the server will be updated to the most recent revision.
•revert@repository-server-update <revision-to>—roll back Dr.Web Server to a certain revision.
|
The last two actions are recorded in the audit log. Update and rollback of Dr.Web Server are described in the administrator's documentation, section Updating Dr.Web Server and Restoring it from Backup. |