Command Line Arguments |
![]() ![]() ![]() |
To launch Dr.Web HTTPD from the command line of the operating system, the following command is used:
Dr.Web HTTPD can process the following options:
Example:
This command outputs short help information on Dr.Web HTTPD. Startup Notes The component cannot be launched directly from the command line of the operating system in an autonomous mode (autonomously from other components). It is launched automatically by the Dr.Web ConfigD configuration daemon when required (usually at the startup of the operating system). If the component is running and the web interface is installed, then to manage the components of Dr.Web for UNIX, you can simply use any standard web-browser to access, via HTTPS, any of the addresses at which the web-interface is served. 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).
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.
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. |