I thought I'd share my final solution with the list. My solution was
to construct the event message on the fly, and use the context to
store it when it's not being manipulated. When the message is built, I
call the built-in logger(1) command to write this to syslog. For some
reason,
--- On Tue, 4/21/09, Michael Hale mh...@transcomus.com wrote:
From: Michael Hale mh...@transcomus.com
Subject: Re: [Simple-evcorr-users] is there a way to alarm when input is NOT
seen after a certain amount of time?
To: Risto Vaarandi risto.vaara...@seb.ee
Cc:
In message 182d6d9a-b79d-4889-b8e0-c90f52001...@transcomus.com,
Michael Hale writes:
On Apr 16, 2009, at 12:14 PM, Risto Vaarandi wrote:
Michael Hale wrote:
Hello,
I was wondering if there was a way to alarm if a certain output is
NOT seen after a certain amount of time.
For example, I
