Daemon Log
Since Dr.Web Daemon is a resident program, information on its operation can be obtained only from a log file. Log file contains details on processing of all scanning request sent to Dr.Web Daemon. You can specify the log file location in a value of the LogFileName parameter.
Dr.Web Daemon can log information to different files depending on a client that sent the request. You can specify different log files for every Dr.Web clients (for example, Dr.Web for UNIX File Servers) in the ClientsLogs parameter value.
Regardless of the ClientsLogs parameter, if Dr.Web Daemon recognizes its client, scanning results will marked with a prefix indicating the client. The following prefixes are available:
•<web> – Dr.Web ICAPD;
•<smb_spider> – Dr.Web Samba SpIDer;
•<mail> – Dr.Web MailD;
•<drwebdc> – console client for Dr.Web Daemon;
•<kerio> – Dr.Web for Kerio Internet Gateways;
•<lotus> – Dr.Web for IBM Lotus Domino.
|
In the FreeBSD operating system, syslog service can intercept information output by Dr.Web Daemon to the console. In this case, the information is logged character-by-character. That occurs when the logging level is set to *.info in the syslog configuration file (syslog.conf). |
Statistics on pool used for processing scanning request is output to the log file upon receipt of SIGUSR1 signal (the signal must be sent only to parent process, as if a child process receives SIGUSR1, it terminates).
Output of statistics on process pool is regulated by the stat value (yes or no), specified for the ProcessesPool parameter. Collected statistics is not aggregated. Each time the saved record contains statistics on the pool state between previous and current moment of saving.
Example of pool statistics output record:
Fri Oct 15 19:47:51 2010 processes pool statistics: min = 1 max = 1024 (auto) freetime = 121 busy max = 1024 avg = 50.756950 requests for new process = 94 (0.084305 num/sec) creating fails = 0 max processing time = 40000 ms; avg = 118646 ms curr = 0 busy = 0
where:
•min – minimal number of processes in the pool;
•max – maximal number of processes in the pool;
•(auto) – displays if limits on number of processes in the pool are determined automatically;
•freetime – maximum idle time for a process in the pool;
•busy max – maximum number of simultaneously used processes, avg - average number of simultaneously used processes;
•requests for new process – number of requests for new process creation (frequency of requests per second is displayed in parenthesis);
•creating fails – number of failed attempts to create a new process (failures usually occur when the system is running low on resources);
•max processing time – maximum time for processing a single scanning request;
•avg – average time for processing a single scanning request;
•curr – number of all current processes in the pool;
•busy – number of currently used processes in the pool.