Previous Topic: How the Kernel Loading Exits WorkNext Topic: Interacting with LDAP


How the Kernel Unloading Exits Work

To let you control operating system and third-party processes, CA ControlMinder lets you automatically make calls to UNIX exits when unloading the CA ControlMinder kernel extension.

When you run SEOS_load -u, CA ControlMinder performs the following actions:

  1. Looks for programs in the following directory:
    ACInstallDir/exits/LOAD
    
  2. Selects all the programs that have file names of the following format:
    SEOS_unload_string.always
    

    Where string can be any descriptive strings.

  3. Executes, in lexicographical order, each file it found in the directory ACInstallDir/exits/LOAD:
    SEOS_load_string.always -pre
    

    Each file is executed with the -pre parameter so that you can write your exits to detect the parameter and perform the actions required before the kernel is unloaded.

    Note: If the exit returns a nonzero value, CA ControlMinder kills the exit process, displays an error message, and aborts the kernel unloading.

  4. Tries to unload the kernel.

    If the kernel does not unload:

    1. Selects all the programs that have file names of the following format:
      	SEOS_unload_string.opt
      
    2. Executes, in lexicographical order, each file it found in the directory ACInstallDir/exits/LOAD:
      	SEOS_unload_string.opt -pre
      

      Each file is executed with the -pre parameter so that you can write your conditional exits to detect the parameter and perform the additional optional actions required before the kernel is unloaded.

      Note: If the exit returns a nonzero value, CA ControlMinder kills the exit process, displays an error message, and aborts the kernel unloading.

    3. Unloads the kernel.
    4. Executes, in lexicographical order, each file it found in the directory ACInstallDir/exits/LOAD:
      	SEOS_unload_string.opt -post
      

      Each file is executed with the -post parameter so that you can write your conditional exits to detect the parameter and perform the additional optional actions required before the kernel is unloaded.

      Note: If the exit returns a nonzero value, CA ControlMinder kills the exit process and displays an error message. Having already been unloaded, the CA ControlMinder kernel remains unloaded.

  5. Executes, in lexicographical order, each file it found in the directory ACInstallDir/exits/LOAD:
    SEOS_unload_string.always -post
    

    Each file is executed with the -post parameter so that you can write your exits to detect the parameter and perform the actions required after the kernel is loaded.

    Note: If the exit returns a nonzero value, CA ControlMinder kills the exit process and displays an error message. Having already been unloaded, the CA ControlMinder kernel remains not loaded.