Linux-UNIX: K-TAP FAQs

Find answers to commonly asked questions about K-TAP.

Does K-TAP support Ksplice (or other live patching mechanisms)?

K-TAP does not support Ksplice or any other live kernel patching mechanism. To use K-TAP in your Linux environment, you must disable live kernel patching, including Ksplice extensions and similar mechanisms, such as Ubuntu Linux livepatch or SUSE Linux Live Patching.

Can one database server be used to build different custom K-TAP versions?

Yes. The module is created for the currently installed kernel on the server, so you must set the correct kernel and restart the server.

Do you need to regenerate and reinstall the custom K-TAP each time that the server receives a new kernel?

Yes.

What happens if the K-TAP is not up to date?

If the KTAP does not match the running kernel, it does not load.

Does a custom K-TAP need to have the same version as the S-TAP, or can a Guardium system have K-TAP and S-TAP that are running different versions?

K-TAPs and S-TAPs must run the same version.

When you install K-TAP by using the Flex method, Guardium determines which precompiled K-TAP is the most suitable for the installation. How is this procedure performed by Guardium?

See Linux-UNIX: S-TAP compilation of K-TAP.