5.4.4.3 Event To Script Notification

The event to script notification add-on calls a user defined script on each event passing the rules filter.

Configuring / installing this feature is a four step procedure:

1. Create a "rules" file. See page The rules file for details about this file.
2. Edit the e2c.properties file for your needs, some information about the settings in this file are given below.
3. Edit the vlc.properties file and set server.addon=EventToScript This line probably is already presented in the file but deactivated by a # character in front of it.
4. restart the MNC service

The e2c.properties file contains the parameters which configure the behavior of the event to script notification. The file follows the Java properties file syntax and may contain thefollowing keys / values:

scriptName - specifies the name of the (Bash-) script or binary excecutable to be executed. The file must be located in the /home/satnms/scripts/ directory on the sat-nms installation. The file must be set readable and executable for the user that shall execute it.

scriptName=e2c-test.sh

ruleFileName - specifies the name of the rule file used by the notification add-on. By default this is rules, you may change this if you like to keep multiple rules files which you want to use alternatively.

ruleFileName=rules

user - if this key is defined, the software does execute the the script with sudo -u <user> <scriptName> ... instead of calling the script directly. You probably have to set the password property as well to make this work. By default, the MNC service (and the Addon) runs as user satnms. So you don't have to specify it again. But if the script requires a different user please use this settings.

user=satnms

password - specifies the login password of the user set with the user property. Its not required if sudo is configured to allow this command for the specified user directly.

password=satnms

verbose is for software tests only. For normal operation this always must be 'false'.

#verbose=true
verbose=false

The file is read once at system start, hence any changes to this file become effective with the next restart of the MNC service.