For Linux and Solaris OS

To run Dr.Web for UNIX File Servers:

1.Register the software.

2.Copy or move the key file to the directory with Dr.Web for UNIX File Servers executable files (the default directory for UNIX systems is %bin_dir). Name of the key file can be different in different distribution packages (for details, see Software Registration):

If Dr.Web for UNIX File Servers was purchased as a standalone product, license key file is named drweb32.key. In this case, copy the file to the %bin_dir directory without changing its name.

If Dr.Web for UNIX File Servers was purchased as a part of Dr.Web Enterprise Security Suite, archive received during registration contains a key file for Dr.Web Enterprise Server (enterprise.key) and a key file for workstations (agent.key). Rename agent.key as drweb32.key and copy it to the %bin_dir directory.

To use a key file from a different location or with another name (for example, agent.key), specify its full path as a Key parameter value in the drweb32.ini configuration file. In the Standalone mode, alternative path to the key file must be specified as a value of the LicenseFile parameter in agent.conf (a configuration file of Dr.Web Agent).

3.Configure the software by making necessary changes to the configuration files. For details on configuration parameters, see the corresponding sections of this Manual.

4.Set 1 as a value of the ENABLE variable in the drwebd.enable file to run Dr.Web Daemon. If it is not required to run Dr.Web Daemon on the local machine (properly configured Dr.Web Daemon is working on another local network computer), the value of the ENABLE variable must be 0 (its default value).

5.Set 1 as a value of the ENABLE variable in the drweb-monitor.enable file to run Dr.Web Monitor.

 

Location of the enable files depends on Dr.Web for UNIX File Servers installation type:

Installation from universal package for UNIX systems:

Files are saved to the %etc_dir directory and named as follows drwebd.enable, drweb-monitor.enable.

Installation from native DEB packages:

Files are saved to the /etc/defaults directory and named as follows drwebd, drweb-monitor.

Installation from native RPM packages:

Files are saved to the /etc/sysconfig directory and named as follows drwebd.enable, drweb-monitor.enable.

 

6.Run Dr.Web Daemon and Dr.Web Monitor either from the console or a file manager of your operation system. After startup, Dr.Web Monitor starts all other Dr.Web for UNIX File Servers components.

In case of installation from native packages in Solaris:

During Dr.Web for UNIX File Servers installation, the SMF service management system attempts to run Dr.Web Monitor. If Dr.Web Monitor cannot find a licence key file (for example, on the first installation of Dr.Web for UNIX File Servers), it stops its operation and SMF goes into the maintenance state.

To run Dr.Web Monitor, reset the maintenance state:

Enter the following command

# svcs -p <FMRI>

where FMRI is a unique identifier of a controlled resource. In this case, a unique identifier of Dr.Web Monitor is required.

Force termination of the process from svcs -p output list.

# pkill -9 <PID>

where PID is a number of the process listed above.

Restart Dr.Web Monitor with the following command:

# svcadm clear <FMRI>

While installing Dr.Web for UNIX File Servers from native packages in Solaris, run Dr.Web for UNIX File Servers with the SMF service management system:

# svcadm enable <drweb-monitor>
# svcadm enable <drweb-daemon>

To stop the service:

# svcadm disable <service_name>

 

Внимание!

The drwebd module can be launched in one of the following two modes:

1.  with the init script (standard launch)

2. with the Dr.Web Monitor

In the second mode, set the ENABLE parameter to 0 in the enable file.

Each of the components can be run independently as well, but note that Dr.Web Agent must be started first since all other modules receive configuration from Dr.Web Agent.