|
In the [SQLite] section, settings for interaction between Dr.Web MailD and SQLite database are specified:
Database = {path to file}
|
Path to the SQLite database file.
|
Default value:
Database =
|
SizeLimit = {integer}
|
Maximum number of strings received in response to a single database request.
When the parameter value is set to 0, maximum number of received strings is not limited.
|
Default value:
SizeLimit = 1
|
Lib = {path to file}
|
Path to the libsqlite3.so library.
|
Default value:
Lib = /usr/lib/libsqlite3.so
|
BusyTimeout = {time in milliseconds}
|
Timeout for Dr.Web MailD (in milliseconds) to make an entry to the database.
|
Default value:
BusyTimeout = 2000
|
SkipDomains = {LookupLite}
|
List of the domains for which query to the database is not required.
This parameter often allows to improve total performance and considerably reduce server load.
Please note that the parameter value is LookupLite.
The parameter value can also be locally overridden in a Lookup.
|
Default value:
SkipDomains =
|
OnError = {ignore | exception}
|
Sets the mode of error handling (errors that occur in Lookup when connecting to the specified data source).
Allowed modes:
•ignore – ignore the error and continue message processing (the error is only logged); •exception – generate an exception which is handled as a message processing error. The handling method corresponds to the ProcessingError parameter value set for the module in operation of which this error occurred. The parameter value can also be locally overridden in a Lookup.
|
Default value:
OnError = ignore
|
Note the following features of using SQLite DBMS:
•Every time when information is written to the database, its file is locked. So, if more than one program is working with the same SQLite database file, it is possible that a writing process cannot obtain exclusive access to the database during the time specified in the BusyTimeout parameter. As a result, the process is aborted with the following error: "Database is locked". •Avoid using GUI for SQLite, as graphical interface can lock the databases for future use. •If an external process locked the database for a long time, statistics export errors can occur. A conflict may also occur if Dr.Web MailD is configured to export different types of statistics into the same SQLite database file and the specified time is too small. •If the SQLite database, that provides settings for several parameters (using Lookup of sqlite type) was not accessible over a period of time and then connection to the database was reestablished, it is necessary to send a SIGHUP signal to drweb-maild module in order to reconnect Dr.Web MailD and SQLite.
|