alarmd - Tool to monitor state transition of client-reported fault conditions

	Commit message (Collapse)	Author	Age
*	Refactor build process, use setup.pyHEAD master	David Phillips	2019-05-08
\|
*	Add alarm change timestamping	David Phillips	2018-08-29
\|
*	Add less ambiguous recipes	David Phillips	2018-08-28
\|
*	Detach per-connection server threads	David Phillips	2018-08-28
\|
*	Fix typo in comment	David Phillips	2018-08-28
\|
*	Handle clients in separate threads, add mutexes	David Phillips	2018-08-28
\|
*	Remove some magic constants	David Phillips	2018-06-27
\| \| \| \|	Also removes old debug print code
*	Refactor client handling code, loop	David Phillips	2018-06-27
\|
*	Remove old byte-order switching code	David Phillips	2018-06-27
\| \| \| \| \| \| \| \|	It's safe enough to assume that UNIX domain sockets imply both ends of the socket have the same represenatations. Anyone doing hackery with forwarding/proxying UNIX domain sockets between systems should know better.
*	Record pid of process regsitering alarm	David Phillips	2018-06-27
\|
*	Remove debug print statements	David Phillips	2018-06-27
\|
*	Refactor libalarm	David Phillips	2018-06-27
\|
*	Refactor raise+clear handlers	David Phillips	2018-06-27
\|
*	Begin server refactor, remove hard-coded sockets	David Phillips	2018-06-27
\|
*	Change from TCP to UNIX sockets, massive clean up	David Phillips	2018-06-27
\|
*	Initial dump of prototype	David Phillips	2018-06-04