User Tools

Site Tools


code:trigger_scripts

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
code:trigger_scripts [2008/09/06 20:54]
127.0.0.1 external edit
code:trigger_scripts [2011/11/06 00:00] (current)
Line 1: Line 1:
 +====== State ======
 +
 +Most of the functionality implemented in rts2-xmlrpcd.
 +
 ====== What is it? ====== ====== What is it? ======
  
-Currently, RTS2 has only one way how to notify external user if something happens - preprogrammed emails can be send. Those are currently ​send on dome events (dome opened, closed, restarted) for some domes and on targets events (target observations started, first image received, observations ended, all images processed). Text of the message is fixed inside RTS2, and to change it, it must be located in code and RTS2 must be recompiled.+Currently, RTS2 has only one way to notify external user if something happens - preprogrammed emails can be sent. Those are currently ​sent on dome events (dome opened, closed, restarted) for some domes and on targets events (target observations started, first image received, observations ended, all images processed). Text of the message is fixed inside RTS2, and to change it, it must be located in code and RTS2 must be recompiled.
  
 It is clear that this approach was far overcome in current RTS2 use. More robust, configurable and modular approach is needed. It is also clear that sending of an warning email can be easily handled by **bash** scripts, or any other scripts, and must not necessary reside inside RTS2. It is clear that this approach was far overcome in current RTS2 use. More robust, configurable and modular approach is needed. It is also clear that sending of an warning email can be easily handled by **bash** scripts, or any other scripts, and must not necessary reside inside RTS2.
code/trigger_scripts.1220727293.txt.gz ยท Last modified: 2009/12/14 00:00 (external edit)