ext_kernel Guide

Home > Books > Adminstrator's Guide to NetKernel > System Modules > ext_kernel Guide

Purpose

The ext_kernel module serves two purposes. It supplies accessors to get and set kernel configuration. It also contains a configurable init process which is called when the kernel starts.

Init Process

The System Tuning Guide describes how any init process can be configured which will be called when the container cold or hot starts. Ext_kernel provides a configurable implementation. The configuration is available via the System Component Accessor netkernel:init-hooks. This URI provides an xml document of the form:

<initHooks>
  <hook>
    <uri>active:module+module@urn:org:ten60:netkernel:ext:introspect+resource@ffcpl:/introspect/init</uri>
    <name>Module Deployment Verification</name>
  </hook>
  <hook>
    <uri>active:module+module@urn:org:ten60:netkernel:ext:install+resource@active:install</uri>
    <name>Module Install/Uninstall Detection</name>
  </hook>
  <hook>
    <uri>active:module+module@urn:org:ten60:netkernel:ext:entrypoint+resource@active:entrypoint-init</uri>
    <name>Entrypoint Maintenance</name>
  </hook>
  <hook>
    <uri>active:module+module@urn:org:ten60:netkernel:ext:install+resource@active:postInstall</uri>
    <name>Post-Install Scripts</name>
  </hook>
</initHooks>

This document can be added to and then written back with a SINK request. This provides a mechanism for modules to add new scripts to be run each time NetKernel starts.

Accessors

See the list of accessors here.