Command Line Arguments

Top  Previous  Next

To run Dr.Web Network Checker, type the following command in the command line:

$ <opt_dir>/bin/drweb-netcheck [<parameters>]

Dr.Web Network Checker can process the following options:

Parameter

Description

--help

Function: Instructs to output short help information about command-line parameters to the console or to the terminal emulator and to exit upon completion.

Short form: -h

Arguments: None.

--version

Function: Instructs to output information about the version of this component to the console or to the terminal emulator and to exit after completion.

Short form: -v

Arguments: None.

Example:

$ /opt/drweb.com/bin/drweb-netcheck --help

This command outputs short help information on Dr.Web Network Checker.

Startup Notes

The component cannot be run directly from the command line of the operating system in an autonomous mode (autonomously from other components). It is run automatically by the configuration daemon Dr.Web ConfigD configuration daemon when required (usually on operating system startup). If a value of the FixedSocketPath parameter in the configuration is specified, the agent is always running and available for clients via the specified UNIX socket. To start scanning via network, you can use the Dr.Web Ctl command-line tool for Dr.Web for UNIX management (it is started by the command drweb-ctl). If there are no configured connections to remote hosts, the local scanning will be started.

To scan an arbitrary file or directory using Dr.Web Network Checker you can use netscan command of Dr.Web Ctl tool:

$ drweb-ctl netscan <path to file or directory>

To request documentation about this component of the product from the command line, use the following command man 1 drweb-netcheck

 

Convention for Paths to Product Files

The product described in the present document is designed for operation in different UNIX-based operating system. Real paths to product files depend on the operating system installed on the user’s computer. For notational convenience, the following conventions are used:

<opt_dir>—directory where main product files are located (including executable files and libraries).

<etc_dir>—directory where the configuration file and a key file are located.

<var_dir>—directory where supporting and temporary product files are located.

Real paths corresponding to the conventions in different operating systems are given in the table below.

OS Type

Convention

Real Path

GNU/Linux,
Solaris

<opt_dir>

/opt/drweb.com

<etc_dir>

/etc/opt/drweb.com

<var_dir>

/var/opt/drweb.com

FreeBSD

<opt_dir>

/usr/local/libexec/drweb.com

<etc_dir>

/usr/local/etc/drweb.com

<var_dir>

/var/drweb.com

For space considerations, examples use paths for GNU/Linux operating systems. In some places of the document, where it is possible, examples contain real paths for all of the operating systems.