-
I have the Dr.Web daemon and a mail filter installed. Sometimes I receive to the administrator address notifications that some message was not checked because The filter cannot connect to the DrWEB daemon. Can it be avoided in future?
-
There might be two reasons for that:
- A jump of loading or a queue of connections to the daemon is over flooded.
- The daemon was inaccessible for some reasons.
And there are two workarounds for these problems. The second one is more universal (for both cases):
- use several sockets between the daemon and the filter. Example of configuration:
drweb32.ini:
Socket = /var/drweb/run/.drwebd
Socket = 3000 localhost
drweb_{mta}.conf: ({mta} = smf, cgp, postfix, exim, qmail, zmailer, courier or mio)
[DaemonCommunication]
Address = local:/var/drweb/run/.drwebd, inet:3000@localhost
This will result in the following: if there is no connection with the first socket (the queue is over flooded), the filter will try to connect to the second one.
- But it is more reliable to use one more active daemon (may be on the same host, but it better on another), which will smooth away load-peaks or inaccessibility of the main daemon. Example
drweb_{mta}.conf: ({mta} = smf, cgp, postfix, exim, qmail, zmailer, courier or mio)
[DaemonCommunication]
Address = local:/var/drweb/run/.drwebd, inet:3000@another.myhost.example.com
Note: local scanning mode (LocalScan = yes) will not function in the filter for the second socket even if that socket is served by the daemon installed on the same host.
Back to F.A.Q.
|
 |
My five cents
|
 |
| |
What is the screen size of your monitor?
|
 |
|
 |
|
 |
|
