KAPERSKY ANTI-VIRUS 5.7 - FOR NOVELL NETWARE Administrator's Manual page 31

31
Setting up the application
If the numbers match, the application kernel – the KAV.NLM module, the antiviral
engine – KAVSCAN.NLM and the anti-virus database will be loaded to the
server's memory. The program kernel controls the antiviral functions of the
application, while the antiviral engine scans files for viruses. The antiviral engine
is loaded to the protected address space. More than one antiviral engine may be
running at the same time. The number of concurrently executed file scan
requests depends upon the number of simultaneously running copies of the
antiviral engine. By default, there are two copies running at the same time. The
user can change this value in the application settings on the Advanced tab (see
section A.3 on page 115), or load additional antiviral engine copies manually
from the server command line (see below).
As a result, Kaspersky Anti-Virus module will be started on the server selected
in the console tree. After the module starts, the real-time scanning and scan on
demand tasks will be started if they are configured to run at application startup
on the server.
After the Kaspersky Anti-Virus module is started on the server, separate
screens display general statistical information on the module operation and
individual information on every active task. The first screen is created when the
module is started; it contains information about the application and statistical
information regarding the module execution (see Figure 9). When a server
scanning task is launched, a new screen is created. The screen name matches
that of the task and it displays the task settings and its execution statistics (see
Figure 10). After the task is completed the screen is removed.
Figure 9. Server screen when the Kaspersky Anti-Virus module is started