## SafeFire Links

### v1.3a

# Plugin Manager Reference

Plugin manager is shared component which is loaded by various UIs to consistently work with plugins. Plugin manager is configured by [plugman] section in configuration file. This section is required because without it the manager will not know which plugins have to be loaded. Also some settings are actually read by UI so they mey be not available in all UIs.

The manager processes the following configuration variables:

Name | Type | Default Value | Description
--- | --- | --- | ---
buzz | boolean | yes | Make beep on a connect/disconnect.
log.console | boolean | yes | Send log text not only to syslog but also to UIs STDERR. See Logging Reference for details.
log.level | decimal | depends on UI | Prints to log only messages with at least this severity. The possible values are: 0 - LOG_EMERG. System is unusable 1 - LOG_ALERT. Action must be taken immediately 2 - LOG_CRIT. Critical conditions 3 - LOG_ERR. Error conditions 4 - LOG_WARNING. Warning conditions 5 - LOG_NOTICE. Normal but significant condition 6 - LOG_INFO. Informational 7 - LOG_DEBUG. Debug messages
input | String |  | Name of an external REXX script. An UI in this mode will read keyboard input from this long running script not from system console.
log.hook | String |  | Pass human readable log messages to the external REXX script with this name. See Message log REXX exit for details.
message.hook | String |  | Name of an external REXX script to process execution status messages. For example such script may manage %ETC%\resolv file accordingly to received address of DNS. See Message processing REXX exit for details.
chain | String |  | Name of configuration file section from which plugin chain will start to load. It is allowed to have several such statements in the configuration section. There are no special restrictions for plugins in a multichained configuration but if you don't have a strong reason to do this it is better to run chains in separate UI processes to simplify general management and to increase data processing stability (processes will die independently on exceptions). The most frequent case when you need a multichained configuration is remote control plugin which can't be inserted to an usual data processing chain.

Return to documentation index | SafeFire Links (C) Link Guard Solutions 1999, 2000