The component is designed to request data from text files, relational databases, network storage and directory services (such as Active Directory) that support LDAP. The received data (for example, user identifiers and rights) is transferred to Dr.Web for UNIX Mail Servers components that requested it to be used for various scanning rules (for example, to allow the user to access a requested URL and so on).
|
This manual does not cover the operating principles of relational databases, Redis storage, directory services and LDAP. If necessary, refer to the corresponding reference materials. |
The Dr.Web LookupD component is started automatically by the Dr.Web ConfigD configuration daemon when required (upon receiving a request for fetching of data from storage).
Having received a request for data from a certain component of Dr.Web for UNIX Mail Servers, the Dr.Web ConfigD configuration daemon starts Dr.Web LookupD (if not started), then the component performs the request from a requested data source and returns a response. Depending on the request, the response is either a list of strings retrieved from the data source according to a given search criteria, or a boolean value (true or false) that indicates whether the search results contain strings that match the given condition.
You can specify an unlimited number of data sources in Dr.Web LookupD settings. When generating a request for data retrieval, the client component of Dr.Web for UNIX Mail Servers must specify the source of data. Once Dr.Web LookupD is started and the request is performed, it continues to operate for some time waiting for new requests. If there are no more requests, Dr.Web LookupD shuts down automatically after a delay.
Other components of Dr.Web for UNIX Mail Servers basically use Dr.Web LookupD for retrieving data to check the validity of custom conditions specified in the operation rules for these components. When checking the applicability of rules and the validity of conditions, data requests to Dr.Web LookupD are performed automatically.
Aspects of processing text files
1.When processing text files, leading and trailing spaces in strings are discarded. Blank strings and strings that have the # character as the first non-whitespace character are ignored.
2.Text files are considered immutable data sources and their content is fully cached in memory. In addition, the results of requests to these files for value validation are also cached. Thus, if the source file has been modified, Dr.Web LookupD must re-read the configuration, which can be done by sending a HUP signal to the Dr.Web ConfigD component, for example, by running the drweb-ctl reload command.
MySQL connection aspects
Before establishing a connection to MySQL, the parameters from the [client] section of the MySQL default settings file are read (the file search is done for the following paths: /etc/my.cnf, /etc/mysql/my.cnf and /etc/alternatives/my.cnf).