opsi manual opsi version 4.0.2 - opsi Download - uib

opsi manual opsi version 4.0.2
7.3.6 Configuration
Configuration of different events
62 / 193
To meet the requirements of the various different situations in which the opsi-client-agent will become active, a slightly
complex configuration is needed. To reduce the complexity, the configuration file uses something like inheritance.
In the opsiclientd configuration section headers like [event_] introduce a new event configuration section.
An event configuration may be disabled by setting the section option active = false.
There are different types of event configurations (type).
• There are event configuration templates (type = template).
Event configurations may inherit configurations from another event. In this case the option super points to the
other event to inherit all parameters from (excluding the parameter active). These inherited parameters may be
overridden by local parameters in the current event section. So an event section needs only those parameters which
are different from the super event.
Setting an event to active = false does not change anything in the inheritance process.
• The other event types are:
– gui startup
A gui startup event starts while booting the client and loading the graphical user interface (GUI). It is the
most used event and set to active in the default configuration.
– custom
Event configurations of the type custom are fired by a wql event. A wql event is defined by the corresponding
wql statement in the event configuration. If the wql statement is empty, the event will never be fired, but can
be executed from the interactive web interface.
– user login
will be fired at the login of a user
– timer
will be fired all interval seconds
– sync completed
will be fired if the synchronisation of configurations (sync_config_from_server) or products (cache_products)
is completed.
– sw on demand
will be fired by the user choosing Start actions now in the software-on-demand web page of the opsiclientd. It
will never be fired if software-on-Demand is not used.
• There are Preconditions
Preconditions define special system states (e.g. a user is logged on). In the opsiclientd configuration a section
header of the form [precondition_] starts the declaration of a Precondition. A Precondition
is true, if all declared options are true. An option not declared (but possible) is assumed as true.
Possible options for Preconditions are:
– user_logged_in: is true if currently a user is logged on.
– config_cached: is true if the caching of configuration data is completed (see: sync_config_from_server).
– products_cached: is true if the caching of product files is completed (see: cache_products).
• A Precondition can be assigned to an event configuration.
If there is a Precondition in an event configuration header, there also must be a configuration for this event
without any precondition. The event configuration with the precondition inherits all the parameters from the event
configuration without precondition.
If the event is fired, first it will be checked which preconditions are true. If there is no precondition true, the
configuration without precondition is used. Is one precondition true, the configuration is used, which is bound to
this precondition. If more than one of the preconditions are true, the most specific event configuration is used
(which is the configuration with the most matching options).