on

Compile the engine if necessary, and activate it.

Because the engine may not have been previously compiled, turning the engine ON may not activate it immediately. Instead, the engine is activated in the background after the compilation.

After turning the engine ON, the engine recompiles and reactivates itself every policy installation regardless of the values of inspect2c_compile and inspect2c_activate.

off

Deactivates the engine if active. Subsequent policy installation on the gateway does NOT auto-activate the engine unless the command is used again.

stat

Print the status of the engine. For example: "During compilation", "Before auto-activation", "Deactivated".

setdefault

Restore control to database settings. Security Management server settings are ignored.

At the next policy installation, return the control of the engine to the values of the following gateway database attributes:

• inspect2c_compile (true/false) - controls whether or not the engine is compiled on the gateway during policy installation. Compilation is performed in the background and may take a few minutes.
• inspect2c_activate (true/false) - controls whether the engine is automatically activated after it is compiled. When set to true, the engine is compiled regardless of the value of inspect2c_compile.

Use GuiDBEdit to change the values of the attributes.