Defining the startup behavior

You can use the UsmUserBase and ReuseEngineBoots properties to define how the probe processes the configuration files on startup.

The following table shows how the values of the properties define the way that the probe processes the configuration files.
Table 1. Defining the probe's startup behavior
Value of UsmUserBase Value of ReuseEngineBoots Probe action

0

0
  1. Generate a replacement for the local engine identifier and store that in the persistent configuration file.
  2. Set the value of engine reboots to one, and store that in the persistent configuration file.
  3. Read the user entries from the non-persistent configuration file, and replace the user entries in the persistent configuration file.

    For any user entries that do not include an engine identifier, use the local engine identifier generated in step 1.

  4. Use the user entries read from the non-persistent configuration file.

1
  1. Increment the value of engine boots and store it in the persistent configuration file.
  2. Read the user entries from the non-persistent configuration file, and replace the user entries in the persistent configuration file.

    For any user entries that do not include an engine identifier, use the local engine identifier read from the persistent configuration file.

  3. Use the user entries read from the non-persistent configuration file.

1

0
  1. Generate a replacement for the local engine identifier and store it in the persistent configuration file.
  2. Set the value of engine reboots to one, and store it in the persistent configuration file.
  3. Use the user entries in the persistent configuration file.

1
  1. Increment the value of engine boots and store it in the persistent configuration file.
  2. Use the local engine identifier in the persistent configuration file.
  3. Use the user entries in the persistent configuration file.

2

0
  1. Generate a replacement for the local engine identifier and store it in the persistent configuration file.
  2. Set the value of engine reboots to one, and store it in the persistent configuration file.
  3. Read the user entries from the non-persistent configuration file and store them in the persistent configuration file in addition to the entries that file already contains.

    For any user entries that do not include an engine identifier, use the local engine identifier generated in step 1.

  4. Use the user entries in the persistent configuration file and the user entries read from the non-persistent configuration file.

1
  1. Increment the value of engine boots and store it in the persistent configuration file.
  2. Read the user entries from the non-persistent configuration file, hash them, and store them in the persistent configuration file in addition to the entries that file already contains.

    For any user entries that do not include an engine identifier, use the local engine identifer from the persistent configuration file.

  3. Use the user entries in the persistent configuration file and the user entries read from the non-persistent configuration file.
Note: This is the procedure that the probe uses when the properties have their default values, and maintains compatibility with previous versions of the probe.