Changes between Version 2 and Version 3 of RT_alarmevent_man
- Timestamp:
- 10/20/08 08:54:20 (5 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
RT_alarmevent_man
v2 v3 30 30 31 31 alarmevent.cfg has 8 arguments that are required: 32 * !Logfile pathwithprefix - the path with a logfile prefix where daily logs will be stored.32 * Logfile pathwithprefix - the path with a logfile prefix where daily logs will be stored. 33 33 * !LoggingLevel n - Set the level of logging the program will do. 0 = off, higher numbers are more verbosity. 34 34 * !LogFile 1 - if 0, no logfile is generated, if 1, then a earthworm style logfile is created 35 35 * !ProgramName ALARM_EVENT - the unique name to allow this module to connect to CMS and be identifed. 36 * !CMSConfig cms.cfg - Points to the cms configuration file which holds all CMS details.36 * CMSConfig cms.cfg - Points to the cms configuration file which holds all CMS details. 37 37 * !UpdateSubject /signals/alarmdevent/update - the name of the CMS signal to use for alarming. 38 38 * DBService dbname - the name of the database being used (for most this will be rtdb or rtdb2) … … 74 74 == MORE INFORMATION == 75 75 76 alarmdec, alarmact, alarmdist are the chain of alarming programs. Alarmevent sends a signal to alarmdec.76 [wiki:RT_alarmdec_man alarmdec], alarmact, alarmdist are the chain of alarming programs. Alarmevent sends a signal to [wiki:RT_alarmdec_man alarmdec]. 77 77
