Command Line Arguments

Top  Previous  Next

To run the configuration daemon Dr.Web ConfigD, type the following command in the command line:

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

The configuration daemon Dr.Web ConfigD 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.

--config

Description: Instructs to use the specified configuration file for further operation.

Short form: -c

Arguments: <path to the file>—the path to the configuration file that you want to use.

--daemonize

Description: Instructs to run the component as a daemon; that is, without access to the terminal.

Short form: -d

Arguments: None.

--pid-file

Description: Instructs to use the specified PID file for further operation.

Short form: -p

Arguments: <path to the file>—the path to a file into which you would like to the process ID (PID) to be Stored.

Example:

$ /opt/drweb.com/bin/drweb-configd -d -c /etc/opt/drweb.com/drweb.ini

The command runs Dr.Web ConfigD as a daemon which uses the following configuration file: /etc/opt/drweb.com/drweb.ini.

Startup Notes

To enable the operation of the product, Dr.Web ConfigD must be running as a daemon. During standard booting, Dr.Web ConfigD is automatically launched when the operating system starts; for this purpose Dr.Web ConfigD comes together with a standard management script located in /etc/init.d. To manage the operation of the component, you can use the Dr.Web Ctl command-line-based management tool for Dr.Web for UNIX (it is called by using the drweb-ctl command).

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

 

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.