NULL Alarm class
Issue #231
closed
ODBedit alarm class is set to ““ (empty) everywhere (in Programs, in Alarm, etc) and I am getting these messages: [mhttpd,TALK] <NULL>: Program ODBEdit is not running.
K.O.
Comments (4)
-
-
reporter yes, this looks right. I cannot find which experiment had this problem to verify ODB settings. grep midas.log does not find this, as MTALK messages are not logged. Closing this bug.
K.O.
-
reporter - changed status to closed
cannot reproduce. K.O.
-
Actually MTALK messages should be logged in my opinion, what do you think? Should we change that? Everything except MDEBUG messages should be logged, right?
- Log in to comment
If /Programs/<name>/Required = y, this means only that the “Programs” page in mhttpd always shows this program, even if not running (background is then red). If /Programs/<name>/Alarm class is ““ (empty), it means “Do not trigger an alarm”. This is done in alarm.cxx:719:
I did not succeed to produce your error message. Can you show me how to do that?