On 2010-05-31T11:45:37, Lars Ellenberg <[email protected]> wrote:
> Use the "anything" resource agent, and define a monitor action script
> of your choice? or put a loop in your script, and restart whatever is
> necessary from there, then let lrm monitor your script, and restart
> that script if necessary?
That is pretty costly in overhead though, and requires something to
actually periodically monitor (ie, it is asynchronous with latency).
> There are so many ways to do it that I really fail to see the challenge?
The suggestion was to register the pids to be monitored with a daemon,
that would then waitpid() for them (or use signal(0) to check them more
frequently), and create event-driven failure notifications with low
overhead.
Regards,
Lars
--
Architect Storage/HA, OPS Engineering, Novell, Inc.
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
"Experience is the name everyone gives to their mistakes." -- Oscar Wilde
_______________________________________________________
Linux-HA-Dev: [email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
Home Page: http://linux-ha.org/
