[Pacemaker] process/service watcher

[Yair Ogen (yaogen)]

No, you understood. The reference you sent seems perfect. Thanks.

Best Regards,

Yair

On Mar 13, 2014 7:28 PM, Frank Brendel <frank.brendel at eurolog.com> wrote:
Maybe I've misunderstood your question.
In a non-clustered environment it doesn't make sense to run pacemaker.

But if you want to use pacemaker for that you can create a resource with a constraint to run only on a specific node.



Regards
Frank


Am 13.03.2014 15:22, schrieb Yair Ogen (yaogen):
Thanks Frank, so you confirm that pacemaker doesn’t offer this?

Yair

From: Frank Brendel [mailto:frank.brendel at eurolog.com]
Sent: Thursday, March 13, 2014 16:05
To: The Pacemaker cluster resource manager
Subject: Re: [Pacemaker] process/service watcher

Hi Yair,

try monit http://mmonit.com/monit/


Regards
Frank
Am 13.03.2014 14:24, schrieb Yair Ogen (yaogen):
Does pacemaker have an option to act as a process / service watcher regardless to being part of a cluster? i.e. watch a process and identify when it’s down and re-start it.

I am looking for a software solution that does this even a non-clustered environment.

Thanks.

Regards,

Yair




_______________________________________________

Pacemaker mailing list: Pacemaker at oss.clusterlabs.org<mailto:Pacemaker at oss.clusterlabs.org>

http://oss.clusterlabs.org/mailman/listinfo/pacemaker



Project Home: http://www.clusterlabs.org

Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf

Bugs: http://bugs.clusterlabs.org




_______________________________________________
Pacemaker mailing list: Pacemaker at oss.clusterlabs.org<mailto:Pacemaker at oss.clusterlabs.org>
http://oss.clusterlabs.org/mailman/listinfo/pacemaker

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20140313/f6a1f333/attachment-0003.html>