Usage Examples |
Usage examples for Dr.Web Ctl (): 1. Object scanning 1.Perform scanning of the /home directory with default parameters:
2.Scan paths listed in the daily_scan file (one path per line):
3.Perform scanning of the boot record on the :
4.Perform scanning of the running processes:
1.2. Scanning of Files Selected by Criteria Examples for selection of files for scanning are listed below and use the result of the operation of the utility . The obtained list of files is sent to the command scan with the parameter --stdin or --stdin0. 1.Scan listed files returned by the utility and separated with the NUL ('\0') character:
2.Scan all files in all directories, starting from the root directory, on one partition of the file system:
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:
4.Scan all files of the root user in all directories, starting from the root directory:
5.Scan files of the root and admin users in all directories, starting from the root directory:
6.Scan files of users with UID in the range 1000–1005 in all directories, starting from the root directory:
7.Scan files in all directories, starting from the root directory, with a nesting level not more than five:
8.Scan files in a root directory ignoring files in subdirectories:
9.Scan files in all directories, starting from the root directory, with following all symbolic links:
10.Scan files in all directories, starting from the root directory, without following symbolic links:
11.Scan files created not later than May 1, 2017 in all directories, starting with the root directory:
1.3. Scanning of Additional Objects 1.Scanning of objects located in the directory /tmp on the remote server 192.168.0.1 by connecting to it via SSH as a user user with the password passw:
2. Configuration management 1.Display information on a current program package, including information about running processes:
2.Output all parameters from the [Root] section of the active configuration:
3.Set 'No' as the value of the Start parameter in the [ClamD] section of the active configuration (this will disable the Dr.Web ClamD component):
Note that superuser privileges are required to perform this action. To elevate the privileges, you can use the command, as shown in the following example:
4.Forbid the update component to perform an update of files 123.vdb and 567.dws:
Note that in this case an option -a is used to add a new value to the already existing list of values of the parameter Update.ExcludedFiles. 5.Remove a file 123.vdb from the list of files, the update of which is prohibited by the update component:
6.Reset the list of files, the update of which is prohibited for the update component, to the default value of:
7.Perform force update of anti-virus components of the product:
8.Restart the configuration of components of the installed Dr.Web program package:
Note that superuser privileges are required to perform this action. To elevate the privileges, you can use the command, as shown in the following example:
9.Connect the product to the server of central protection, operating on the 192.168.0.1 host under the condition that a public key of the server is located in file :cskey.pub |