From Danny Flippo, when the scheduler goes into its defensive "dead" state, start sending emails over and over. Allow the user to set the interval and count (up to "forever") of those messages. Also provide for an optional "urgent" message email address to which those messages could also be sent (as a text message).

 

  
SVN Comment
 
 

  
Author
  
rbdenny
 
 

  
Repository
  
svn+ssh://rbdenny@a2_svn_dc3/home/rbdenny/svn/astro/scheduler
 
 

  
SVN Revision
  
406
 
 

  
Affected files
  
/trunk/Help/Advanced.htm (Modified)
/trunk/Help/RelNotes.htm (Modified)
/trunk/Scheduler/ConfigForm.cs (Modified)
/trunk/Scheduler/Engine.cs (Modified)
/trunk/Scheduler/MainForm.cs (Modified)

 
 

  
Check-in comment
  
run a program when the dispatcher enters "dead" state. Users no longer see "dead", instead "operator intervention required". Other changes around this. GEM:1242
GEM:986

 

This issue came up again in this Comm Center thread by Peter Prendergast. I proposed to fire off a command line (ShellExec()) when the scheduler goes Dead.



I upped the priority of this. It needs to be done now.