3. How to Set Configuration Options

3.1. Unix SysV-style service.
3.2. Windows service.
3.3. Compile-time customisation

This section tells you how to set configuration options, not what options are available. For a detailed description of the available configuration options, see the omniEvents reference section.

See also the eventc reference section, for a description of how to configure new event channels at run-time.

omniEvents' default “out of the box” set-up is fit for most purposes. You only need to modify the configuration if you are interested in advanced features such as fault tolerant failover, or changing the default TCP port.

In general, command-line parameters are stored somewhere, and retrieved each time the daemon is started. The method of storing parameters is different on Unix and Windows. In addition, there are a number of defaults that can be set at compile-time.

3.1. Unix SysV-style service.

The SysV init program starts the omniEvents daemon from the script /etc/init.d/omniorb-eventservice. You can also use this script to start and stop the service manually:

syntax: /etc/init.d/omniorb-eventservice [start|stop|restart]

The script reads omniEvents' configuration options from the file /etc/default/omniorb-eventservice. Edit this file to change the options.

See also: omniEvents reference.

3.2. Windows service.

The omniEvents Windows service stores options in the Registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\omniEvents. They are read each time the service starts. Usually the only option you should set is the -t FILENAME option that directs trace output to the named file.

You set the service options by listing them after the install or setoptions commands:

syntax: omniEvents install OPTIONS

syntax: omniEvents setoptions OPTIONS

You can see the currently stored options with the getoptions command:

syntax: omniEvents getoptions

See also: omniEvents-win32 reference.

3.3. Compile-time customisation

Some compile-time parameters may only be adjusted by manually editing the file src/defaults.h:

  • the default data directory [/var/lib/omniEvents on Unix, C:\omniEvents on Windows.]

  • the name of the environment variable that sets the data directory [OMNIEVENTS_LOGDIR]

  • the period between data file checkpoints [900 seconds]

  • Default event channel parameters:

    PullRetryPeriod_ms Time between pull() calls. [1 second]
    MaxQueueLength Number of events to queue. [1023]
    MaxNumProxies Limit on number of ProxyPullSuppliers. [1024]
    CyclePeriod_ns Time between batch transfer of events. [0.1 second]

Please refer to the src/defaults.h file for descriptions of all parameters.