About the configuration file (Feed Utility)

April 11, 2024

ID 174902

Feed Utility reads settings from a configuration file.

Editing the configuration file

If the configuration file is absent or does not follow the rules specified in this section, Feed Utility does not start and it prints an error message.

To avoid potential issues, make a backup copy of the Feed Utility configuration file before you make any changes in the file. If Kaspersky CyberTrace does not work properly after you have reconfigured Feed Utility, replace the configuration file with its backup copy.

Configuration file location (Linux)

In Linux, the configuration file used by Feed Utility is named kl_feed_util.conf and is located in the %service_dir%/etc directory.

Configuration file location (Windows)

The configuration file used by Feed Utility is named kl_feed_util.conf and is located in the same directory as the Feed Utility binary file, %service_dir%/bin.

Encoding requirements

The Feed Utility configuration file, including all paths specified in it, must be in UTF-8 encoding. If you use non-ASCII symbols in the configuration file, and the file is not in UTF-8 encoding, Feed Utility will not start.

Case sensitivity

All the names used in the configuration file (for example, pattern names or feed fields) are case-sensitive.

Using special characters

The Feed Utility configuration file is an XML file. If you need to use characters that are reserved for XML markup (an ampersand, angle brackets, or quotes), enclose the value with such characters in a CDATA section.

The following is an example of a CDATA section in the kl_feed_util.conf file:

<Example><![CDATA[parameter="value"]]></Example>

Absolute and relative paths

When defining directories and files used by Feed Utility, you can use absolute and relative paths. If a relative path is specified, it is calculated from the directory that contains the Feed Utility binary file.

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.