User Guide

74 Kaspersky Anti-Virus® for Sendmail with Milter API

7.14. Restarting Kaspersky Anti-

Virus

Occasionally events occur which necessitate that the application is restarted:

these include configuration changes and application errors. Depending on the

situation, the following methods may be used:

• Configuration changes.

For new changes to take effect, you need to restart Kaspersky Anti-Virus

using the kavmilter service script. The configuration file with the most

recent changes will be reloaded.

To control the application, use the following command line options:

start – check whether Kaspersky Anti-Virus is running (using the

process ID). If the application is running, the kavmilter script is

stopped. If the application is not yet running, the kavmilter script

starts and checks for the necessary changes in the Sendmail

configuration required for successful integration of the mail system

with the anti-virus scanner. If these configuration changes are

made, the anti-virus filter is initiated. A return code of 0 means that

the filter has successfully started.

stop – check whether Kaspersky Anti-Virus is running (using the

process ID). If the application is running, the SIGTERM signal is

executed. If the application does not start within three seconds,

SIGKILL is executed. A return code of 0 means that the application

has been stopped.

restart – stop and start the application again, according to the

procedure initiated by the stop and start options.

reload – restart the application configuration and the anti-virus

database, using the SIGUSR1 signal.

bases – reload only the anti-virus database, and check the license key

validity;

status – check whether Kaspersky Anti-Virus is running (using the

process ID) and output the application status on the console. If the

application is running, the return code is 0; if it is not running, the

return code is 1.

stats – write kavmilter statistics data to the predefined file.

check – check whether Kaspersky Anti-Virus is running. The procedure

is similar to using the status option, but the application status is not

output to the console. The return codes are the same.

• Problems encountered during application operation.