Use Kernel Module for SpIDer Guard

In this section:

•General Information.

•Building the Kernel Module.

•Possible Build Errors.

General Information

If the operating system does not support the fanotify mechanism used by SpIDer Guard for monitoring actions on file system objects, it can use a special loadable module in kernel space (additionally, the kernel module can be used when the fanotify mechanism is implemented with restrictions on access to the file system).

By default, SpIDer Guard is supplied with a completely built loadable kernel module for all operating systems listed in the System Requirements and Compatibility section. In addition, you can build a loadable kernel module manually using the source codes supplied with SpIDer Guardin a tar.bz2 archive.

The archive with source codes is located in the share/drweb-spider-kmod/src/ subdirectory of the Dr.Web for UNIX File Servers base directory <opt_dir> (for GNU/Linux: /opt/drweb.com). The archive’s name is as follows: drweb-spider-kmod-<version>-<date>.tar.bz2.

The drweb-spider-kmod directory also contains the check-kmod-install.sh script. Run the script to check whether your OS supports kernel versions included in Dr.Web for UNIX File Servers. If not, a message prompting to manually build the module is displayed on the screen.

If the drweb-spider-kmod directory is missing at the specified path, install the drweb-spider-kmod package (from repository or using custom installation from universal package, depending on the method you selected to install Dr.Web for UNIX File Servers).

Building the Kernel Module

1.Unpack the archive with source codes to any directory. For example, the following command

unpacks the source codes to the created directory. This directory has the archive name and is created in the same location where the archive resides.

2.Go to the created directory and execute the following command:

If an error occurs during the make command execution, resolve the issue (see below) and restart compilation.

3.After successful execution of the make command, enter the following commands:

4.After the kernel module is successfully compiled and registered on the system, perform additional configuration of SpIDer Guard. Set the component to operate with the kernel module by executing the following command:

It is also possible to specify AUTO instead of LKM. In this case, SpIDer Guard will automatically try to use either the kernel module or the fanotify monitoring interface. For details, type the following command:

Possible Build Errors

While the make command is being executed, errors may occur. If so, check the following:

•To ensure successful building of the module, Perl and GCC are required. If they are missing on the system, install them.

•On certain OSes, you may need to install the kernel-devel package before starting the procedure.

•On certain operating systems, the procedure can fail because the path to the directory with source codes was incorrectly defined. If so, specify the make command with the KDIR=<path to kernel source codes> parameter. Typically, the source codes are located in the /usr/src/kernels/<kernel version> directory.