Usage Examples

This section contains examples of using the Dr.Web Ctl utility (drweb-ctl):

•Object Scanning:

▫Simple Scanning Commands

▫Scanning of Files Selected by Criteria

▫Scanning of Additional Objects

•Configuration Management

•Threat Management

•Example of Operation in Autonomous Instance Mode

1. Object Scanning

1.1. Simple Scanning Commands

1.Perform scanning of the /home directory with default parameters:

$ drweb-ctl scan /home

2.Scan paths listed in the daily_scan file (one path per line):

$ drweb-ctl scan --stdin < daily_scan

3.Perform scanning of the boot record on the sda drive:

$ drweb-ctl bootscan /dev/sda

4.Perform scanning of the running processes:

$ drweb-ctl procscan

1.2. Scanning of Files Selected by Criteria

Examples for file selection for scanning are listed below and use the result of the find utility operation. The obtained list of files is sent to the drweb-ctl scan command with the --stdin or --stdin0 parameter.

1.Scan listed files returned by the find utility and separated with the NUL (\0) character:

$ find -print0 | drweb-ctl scan --stdin0

2.Scan all files in all directories, starting from the root directory, on one partition of the file system:

$ find / -xdev -type f | drweb-ctl scan --stdin

3.Scan all files in all directories, starting from the root directory, with the exception of the /var/log/messages and /var/log/syslog files:

$ find / -type f ! -path /var/log/messages ! -path /var/log/syslog | drweb-ctl scan --stdin

4.Scan all files of the root user in all directories, starting from the root directory:

$ find / -type f -user root | drweb-ctl scan --stdin

5.Scan all files of the root and admin users in all directories, starting from the root directory:

$ find / -type f \( -user root -o -user admin \) | drweb-ctl scan --stdin

6.Scan all files of the users with UID within the range of 1000–1005 in all directories, starting from the root directory:

$ find / -type f -uid +999 -uid -1006 | drweb-ctl scan --stdin

7.Scan files in all directories, starting from the root directory, with a nesting level of no more than five:

$ find / -maxdepth 5 -type f | drweb-ctl scan --stdin

8.Scan files in a root directory while ignoring files in subdirectories:

$ find / -maxdepth 1 -type f | drweb-ctl scan --stdin

9.Scan files in all directories, starting from the root directory, while following all symbolic links:

$ find -L / -type f | drweb-ctl scan --stdin

10. Scan files in all directories, starting from the root directory, without following symbolic links:

$ find -P / -type f | drweb-ctl scan --stdin

11. Scan files created no later than May 1, 2017 in all directories, starting from the root directory:

$ find / -type f -newermt 2017-05-01 | drweb-ctl scan --stdin

1.3. Scanning of Additional Objects

1.Scanning of objects located in the directory /tmp on the remote host 192.168.0.1 by connecting to it via SSH as the user user with the password passw:

$ drweb-ctl remotescan 192.168.0.1 /tmp --Login user --Password passw

2. Configuration Management

1.Display information about the current set of Dr.Web for UNIX File Servers components, including information about running components:

$ drweb-ctl appinfo

2.Output all parameters from the [Root] section of the active configuration:

$ drweb-ctl cfshow Root

3.Set No as the value of the Start parameter in the [LinuxSpider] section of the active configuration (this will disable SpIDer Guard):

# drweb-ctl cfset LinuxSpider.Start No

Note that superuser privileges are required to perform this action. To elevate the privileges, you can use the sudo command, as shown in the following example:

$ sudo drweb-ctl cfset LinuxSpider.Start No

4.Force update of anti-virus components of Dr.Web for UNIX File Servers:

$ drweb-ctl update

5.Restart the component configuration of Dr.Web for UNIX File Servers:

# drweb-ctl reload

Note that superuser privileges are required to perform this action. To elevate the privileges, you can use the sudo command, as shown in the following example:

$ sudo drweb-ctl reload

6.Connect Dr.Web for UNIX File Servers to a centralized protection server operating on host 192.168.0.1 if a server certificate is stored in the /home/user/cscert.pem file:

$ drweb-ctl esconnect 192.168.0.1 --Certificate /home/user/cscert.pem

7.Connect Dr.Web for UNIX File Servers to the centralized protection server using the install.cfg configuration file:

$ drweb-ctl esconnect --cfg <path to install.cfg>

8.Disconnect Dr.Web for UNIX File Servers from the centralized protection server:

# drweb-ctl esdisconnect

Note that superuser privileges are required to perform this action. To elevate the privileges, you can use the sudo command, as shown in the following example:

$ sudo drweb-ctl esdisconnect

9.View the last log records made by the drweb-update and drweb-configd components in the Dr.Web for UNIX File Servers log:

# drweb-ctl log -c Update,ConfigD

3. Threat Management

1.Display information on detected threats:

$ drweb-ctl threats

2.Quarantine all files containing non-neutralized threats:

$ drweb-ctl threats --Quarantine All

3.Display the list of quarantined files:

$ drweb-ctl quarantine

4.Restore all quarantined files:

$ drweb-ctl quarantine --Restore All

4. Example of Operation in Autonomous Instance Mode

1.Scan files and process quarantine in autonomous instance mode:

$ drweb-ctl scan /home/user -a --OnKnownVirus=Quarantine
$ drweb-ctl quarantine -a --Delete All

The first command will scan files in the /home/user directory in autonomous instance mode. Files containing known viruses will be quarantined. The second command will process quarantine content (in autonomous instance mode as well) and remove all quarantined objects.