Specifying paths to plug-ins and libraries

Before the kavicapd service is ready to run, the following paths must be specified:

• Plug-in path

  Path to a directory with PPL plug-in files.

• Library path

  Path to a directory with shared libraries.

The paths to plug-ins and shared libraries can be specified by exporting the KL_PLUGINS_PATH and LD_LIBRARY_PATH environment variables, respectively.

The KL_PLUGINS_PATH and LD_LIBRARY_PATH variables can be exported manually, or automatically by using the ICAP systemd unit file. You can also use the kavicapd.sh shell script, which exports KL_PLUGINS_PATH and LD_LIBRARY_PATH and starts the kavicapd service.

Specifying the path to plug-ins and libraries manually

This method requires exporting the variables each time before you start the kavicapd service in a new session (the variables only exist during the current shell session).

The following example shows how to export the variables manually:

[user@host ~]$ export KL_PLUGINS_PATH="/opt/kaspersky/ScanEngine/ppl" [user@host ~]$ export LD_LIBRARY_PATH="/opt/kaspersky/ScanEngine/lib:${KL_PLUGINS_PATH}:${LD_LIBRARY_PATH}"

Specifying the path to plug-ins and libraries with the kavicapd.sh shell script

You can modify kavicapd.sh so that it exports the variables automatically.

To export the variables by means of the kavicapd.sh shell script:

1. Open kavicapd.sh for editing and locate the following lines:

   SDK_PATH=$PWD/../../../.. KL_PLUGINS_PATH=$SDK_PATH/ppl LD_LIBRARY_PATH=$SDK_PATH/lib:$KL_PLUGINS_PATH:$LD_LIBRARY_PATH

2. Change the values of SDKPATH, KL_PLUGINS_PATH, and LD_LIBRARY_PATH to point to the location of the KAV SDK directory, plug-in directory, and libraries directory, respectively.

The kavicapd.sh shell script will export the variables when it is executed.

Page top