Ticket #37 (closed defect: fixed)

Opened 5 years ago

Last modified 5 years ago

alarmevent has TSS bindings still and receives a CMS signal

Reported by: pfriberg Owned by: pfriberg
Priority: major Milestone: RT LeapSecond build 1
Component: alarming-thread Version:
Keywords: Cc:

Description

alarmevent should only publish CMS signals and all TSS related configuration and other code should be removed. It appears that alarmevent has been causing problems on craton and causes the alarming to seize up. It could be that some queue is being filled but not being responded to by alarm event since it should not be receiving signals. It should only be a publisher.

Change History

comment:1 Changed 5 years ago by pfriberg

  • Status changed from new to closed
  • Resolution set to fixed

Kalpesh redid the code and it is now in the leap-second-dev-branch and now works.

Note: See TracTickets for help on using tickets.