Changing variables in the ICAP mode unit file

March 5, 2024

ID 192475

You can configure Kaspersky Scan Engine by changing one or more variables in its unit file, %distr_kit%/etc/kavicapd.service.

Changing the path to the Kaspersky Scan Engine PID file

You can change this variable if you want to create a PID file of Kaspersky Scan Engine in a directory other than /var/run/kavicapd.pid.

The following example shows how this variable is set in the unit file:

PIDFile=/var/run/kavicapd.pid

Changing environment variables

You must change these environment variables if Kaspersky Scan Engine is located in a directory other than /opt/kaspersky/ScanEngine.

The unit file uses the following environment variables:

  • SDKPATH—Specifies the directory where Kaspersky Scan Engine is located. The following example shows how this variable is set in the unit file:

    Environment=SDKPATH=/opt/kaspersky/ScanEngine

  • KL_PLUGINS_PATH—Specifies the path to the directory containing the PPL plug-in files used by Kaspersky Scan Engine. The following example shows how this variable is set in the unit file:

    Environment=KL_PLUGINS_PATH=/ppl

  • LD_LIBRARY_PATH—Specifies the path to the directory containing shared libraries used by Kaspersky Scan Engine. The following block shows how this variable is set in the unit file:

    Environment=LD_LIBRARY_PATH=/lib:/ppl

Changing paths in the command executed on kavicapd startup

You must change paths in the command executed on kavicapd startup if you put the kavicapd executable file or the ICAP mode configuration file in directories different from the ones specified in the unit file, or if you want to create a PID file of Kaspersky Scan Engine in a directory other from /var/run/kavicapd.pid.

The following example shows how this command is set in the unit file:

ExecStart=/bin/sh -c 'cd ${SDKPATH}/bin; ./kavicapd -c /etc/kavicapd.xml -p /var/run/kavicapd.pid'

Did you find this article helpful?
What can we do better?
Thank you for your feedback! You're helping us improve.
Thank you for your feedback! You're helping us improve.